Capstone: Coin Quest

The capstone turns each isolated lesson into one playable path: a player enters, collects a validated coin, sees a responsive count, reaches a checkpoint, and can extend persistence later.

Shared modules define safe configuration. A bootstrap initializes and starts server services. The server owns coin state and sends approved updates. The client HUD presents those updates and cleans its connections.

The Studio Companion checks only marked capstone targets and public cases. Persistence remains an optional extension because production saving requires more architecture than this prototype.

--!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.

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

{ } is read as “opening and closing braces”: it creates a table value around its entries.

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

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

. is read as “dot”: it accesses a named property or table field.

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: The bootstrap requests the two containers it coordinates.

Line 6: The authoritative service stays server-only.

Line 7: Safe immutable configuration is shared.

Line 9: Init receives explicit dependencies.

Line 12: The feedback RemoteEvent is injected from a fixed path.

Line 14: Start begins behavior only after configuration is complete.

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: The prototype completes one validated collection path, updates local UI, and keeps unrelated place work untouched.

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