LUA objects and classes

Models, properties, methods, constructors, encapsulation, and object design.

Chapter goal: Models, properties, methods, constructors, encapsulation, and object design.

Simple explanation

A class is a blueprint. An object is one real value created from that blueprint, with its own data and behavior.

In LUA, this chapter is about grouping data with behavior. 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

Objects let programs describe real concepts instead of passing loose values everywhere. 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 classes or objects for users, orders, lessons, API responses, game entities, and reusable services.

Example code

local lesson = {
  title = "Loops",
  minutes = 20
}

print(lesson.title)

Line-by-line explanation

• local lesson = { — This stores or updates lesson. The value on the right is worked out first, then saved under that name.
• title = "Loops", — This stores or updates title. The value on the right is worked out first, then saved under that name.
• minutes = 20 — This stores or updates minutes. The value on the right is worked out first, then saved under that name.
• print(lesson.title) — This is the visible output line. It shows the final value after the earlier work is complete.

What the output means

The example creates one lesson object. Add a print call to display its title.

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 lesson = nil -- a class blueprint is confused with one object
  title = "Loops",
  minutes = 20
}

print(lesson.title)

This version intentionally shows how a class blueprint is confused with one object. The changed assignment stores a missing value, or a required line is removed, so later code cannot complete its job safely.

Fixed version

local lesson = {
  title = "Loops",
  minutes = 20
}

print(lesson.title)

The corrected version restores the real value or required operation. It fixes the chapter-specific problem: a class blueprint is confused with one object.

Common mistakes

• Putting every function into one giant class.
• Exposing fields that should be protected by methods.
• Creating inheritance when composition would be simpler.

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

• User profiles.
• Course chapters.
• Inventory items and payment records.

Practice exercise

1. Add one property to the class.
2. Create two objects with different values.
3. Add one small method that uses object data.

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. Is a class a blueprint or an object?
2. What does a constructor create?
3. Which data belongs to each individual object?

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 error handling and debugging. Before opening it, explain this chapter out loud in under one minute.