Get 1Click Maker

User Variables โ€‹

User variables are the boxes you create: a state, a counter, a mode, a saved position. They always start with $ when used in a condition or action: $state, $count, $mode.

Types โ€‹

TypeHoldsExample
StringText (up to 512 characters)OFF, red, Hello
IntegerWhole numbers0, 42, -3
FloatDecimal numbers1.5, 3.14
VectorThree numbers<128, 64, 22>
KeyA UUIDa1b2c3d4-โ€ฆ

Choose the type that matches what you will compare. Integers and floats can be compared with each other; a string cannot be compared with a number.

Naming โ€‹

  • Up to 30 characters: letters, numbers and _. Spaces become _.
  • Names must be unique in the project.
  • In fields, always write the prefix: $state, not state. Without $ the panel treats the text as a literal value.

What you can do with them today โ€‹

  • Compare them in conditions: $state == ON, $count >= 3.
  • Change them with Change Variable: set, add, subtract, or copy another variable's value.
  • Initialize them with a starting value that is restored when the project is built.

Not yet possible: inserting a variable's value into a message, a URL or a texture field. That integration is planned.

Memory โ€‹

Each variable costs 30 units of project memory. A handful is nothing; hundreds add up. Create what you need, delete what you stop using.

Persistence โ€‹

Variables live in the object's memory. Their values survive being attached, detached and rezzed. They reset to their initial value when you Build, so test sequences from a clean state by building again.