LUA arrays, lists, maps, and sets

Store many values, choose the right collection, and transform data safely.

Chapter goal: Store many values, choose the right collection, and transform data safely.

Simple explanation

A collection is a row of storage boxes. It keeps related values together so the program can add, find, remove, or process them.

In LUA, this chapter is about organizing many related values. Start with the idea above. Then connect each symbol to a value or action in the example.

Do not try to remember every symbol. First ask what data the program has, what it does with that data, and what result it creates. Technical words become easier when you connect them to those three questions.

Why this topic is important

Most real apps are data moving through collections. In LUA, the syntax may look different from other languages, but the thinking skill transfers: name the data, choose the right operation, and make the next step obvious.

When to use it

Use collections for users, products, lessons, messages, settings, and search results.

Example code

local lessons = {"types", "loops", "functions"}
local progress = {types = true, loops = false}

print(lessons[1])
print(progress.types)

Line-by-line explanation

• local lessons = {"types", "loops", "functions"} — This stores or updates lessons. The value on the right is worked out first, then saved under that name.
• local progress = {types = true, loops = false} — This stores or updates progress. The value on the right is worked out first, then saved under that name.
• print(lessons[1]) — This is the visible output line. It shows the final value after the earlier work is complete.
• print(progress.types) — This is the visible output line. It shows the final value after the earlier work is complete.

What the output means

types

The output is evidence that the program followed the instructions. If your result is different, read from the first line and write down how each value changes. That is debugging, not failure.

Mistake example

local lessons = nil -- a required input, failure path, or responsibility is unclear
local progress = {types = true, loops = false}

print(lessons[1])
print(progress.types)

The code assumes item 99 exists. Reading outside a collection can throw an error or produce an invalid value.

Fixed version

local lessons = {"types", "loops", "functions"}
local progress = {types = true, loops = false}

print(lessons[1])
print(progress.types)

The corrected version uses a valid item position or a safe collection operation.

Common mistakes

• Using a list when lookup by key should be a map.
• Trusting indexes without checking bounds.
• Duplicating data that should live in one source of truth.

Warning: Change one part at a time. If you change many lines together, it becomes harder to learn which change caused the result.

Real use cases

• Shopping carts.
• Leaderboards.
• Topic catalogs and lesson lists.

Practice exercise

1. Add one item.
2. Remove one item safely.
3. Find an item without assuming its index exists.

Tip: If the exercise feels too large, complete only steps 1 to 3. Small working code teaches more than a large unfinished project.

Mini quiz

1. What is the first valid index?
2. When is a map better than a list?
3. What can happen when an index is outside the collection?

How to read AI-generated code

Do not copy AI code first. Read it like a detective. Find the data, follow the changes, and locate the final output. Ask AI to explain a line only after you have made your own guess.

• What data goes in?
• What values are stored?
• What calculation or decision happens?
• What is printed, displayed, saved, or returned?
• What can go wrong?
• Can you rename one value and still explain the code?

RedM safety check

RegisterCommand creates a named command. Its callback receives source (who triggered it) and args (the words after the command). Client code handles the local player's screen and input. Server code owns trusted game state. Never trust prices, rewards, permissions, or item counts sent by a client; check them again on the server.

Before you move on

• I can explain this topic in my own words.
• I can read the small example without AI.
• I can change the example and predict the new result.
• I can find and fix one simple mistake.
• I can name one real project that uses this idea.

Next topic

Next, learn objects and classes. Before opening it, explain this chapter out loud in under one minute.