LUA functions and reusable logic

Parameters, return values, scope, pure helpers, and naming functions by intent.

Chapter goal: Parameters, return values, scope, pure helpers, and naming functions by intent.

Simple explanation

A function is a small machine. You give it input, it performs one named job, and it can return a result.

In LUA, this chapter is about packaging repeated behavior into named, testable units. 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

Functions are how large programs stay readable and changeable. 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 functions when a block of code has a clear job, is repeated, or deserves a name.

Example code

local function grade(score)
  if score >= 80 then
    return "strong"
  end
  return "practice"
end

print(grade(92))

Line-by-line explanation

• local function grade(score) — This defines a reusable function. Its name describes the job that other code can call.
• if score >= 80 then — This checks a true-or-false condition. The controlled block runs only when that condition is true.
• return "strong" — This sends a result back to the code that called the function. Returning is different from printing.
• end — This line supports a reusable job with an input and result. Read it together with the block directly around it.
• return "practice" — This sends a result back to the code that called the function. Returning is different from printing.
• end — This line supports a reusable job with an input and result. Read it together with the block directly around it.
• print(grade(92)) — This is the visible output line. It shows the final value after the earlier work is complete.

What the output means

Pass

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 function grade(score)
  if score >= 80 then
  end
end

print(grade(92))

The function calculates or chooses a result but never returns it to the caller.

Fixed version

local function grade(score)
  if score >= 80 then
    return "strong"
  end
  return "practice"
end

print(grade(92))

The corrected function returns its result so the caller can store, display, or test it.

Common mistakes

• Making functions do too many unrelated things.
• Returning unclear values like true without context.
• Relying on hidden global state.

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

• Validation helpers.
• Formatters.
• Business rules and scoring systems.

Practice exercise

1. Add a parameter.
2. Return the result instead of printing inside the function.
3. Call the function with two different inputs.

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 a parameter?
2. What does return send back?
3. Why should a function have one clear job?

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 arrays, lists, maps, and sets. Before opening it, explain this chapter out loud in under one minute.