Adding, finding, and removing list values

An inventory list changes as Coin Quest items are collected and used. Safe helpers preserve array order.

table.insert adds while maintaining sequence shape. table.find returns an index or nil. table.remove needs a valid index.

Guard the nil result before removal so an absent item does not become an invalid position.

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

~= is read as “not equal”: it asks whether two values differ.

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.

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

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

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: items begins as a two-value array.

Line 4: table.insert appends Lantern.

Line 6: table.find returns Key's index or nil.

Line 7: The guard proves an index exists.

Line 8: table.remove closes the sequence gap.

Line 11: Two items remain.

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: Missing and present searches both finish without an invalid removal.

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