Updating values with compound assignment

Coin counts rise, timers fall, multipliers grow, and shared rewards divide. Compound assignment states those updates directly.

Read coins += 5 as: “Take the current value in coins, add 5, and store the result back in coins.” Luau reads 10, calculates 10 + 5 as 15, then stores 15.

The longer equivalent is coins = coins + 5. The coins on the right reads the old value, + 5 calculates a new value, and = stores that new value into the name on the left. This line runs once each time execution reaches it.

--!strict asks Studio to check your code for type mistakes. It is an instruction for the editor and produces no Output message.

print(...) calls the built-in print function. Put the values to show inside its parentheses; separate multiple values with commas. Read the result in Studio's Output panel.

local is read as “local”: it creates a name that is available only in the current code scope.

+= is read as “plus equals”: it reads the current value, adds, then stores the result back.

= is read as “is assigned”: it evaluates the right side and stores that value in the name on the left.

Read one statement at a time: name the value being read, what the operation does, and where its result goes. Keep identifiers exactly as written so you can find them again in the code.

Pause at calls, conditions, and loops. Explain when the body runs before moving to the next statement; use the line notes above when a symbol is unfamiliar.

Begin at the first executable statement. Comments and blank lines do not run; a branch chooses which block runs, and a loop may revisit its body.

Line 3: Before the update, coins stores the number 10.

Line 5: Step 1 reads 10, step 2 calculates 10 + 5 as 15, and step 3 stores 15 back in coins.

Line 7: Output reads the new stored number: 15.

Before running, identify the starting values and any existing Studio objects this example needs. List what you expect to change.

After your practice change, check this result: You can name the value after each update and verify it in Output.

Reading or printing a value leaves it unchanged. Look for assignments, calls that change state, and property updates to explain each change you observe.