What runs on the server and what runs on the client

A Coin Quest player should not award their own currency, but their device should control responsive local HUD effects.

The server decides shared game truth: currency, damage, inventory, and purchases. A client handles local input, camera, and presentation.

Replication shares supported state, but a request from a client is still a claim the server must validate.

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

Matching quotes such as "hello" surround a string: a piece of text. The quotation marks tell Luau where the text starts and ends.

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.

if is read as “if”: it starts a decision by evaluating a condition.

then is read as “then”: it marks the body that can run when the condition is truthy.

else is read as “else”: it provides the fallback branch.

end is read as “end”: it closes a block such as a decision, loop, or function.

: is read as “colon”: it calls a method with the object supplied as the first receiver value.

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: RunService exposes the current execution context.

Line 5: IsServer asks whether this code is in server context.

Line 6: The server branch names its authority.

Line 8: The alternative describes client context.

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: Each responsibility has a reason tied to authority or presentation.

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