Dictionaries: values with named keys

Coin Quest configuration is clearer as coinConfig.points than as an unexplained numeric position.

A dictionary maps a key to a value. Dot syntax is concise for identifier-shaped string keys; brackets handle dynamic or non-identifier keys.

Keys describe roles, so dictionary order is not the main meaning.

--!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 “opening and closing braces”: it creates a table value around its entries.

= 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 table groups related configuration.

Line 4: points is a named key mapped to a number.

Line 5: The unit appears in respawnSeconds.

Line 6: isEnabled holds a boolean setting.

Line 9: Dot syntax reads two named fields.

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: Every configuration value has a descriptive key and expected type.

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