Chapter 4: The Brains of the Operation

The Brains of the Operation 🧠

When the creator of Space Invaders first built his game in 1978, he accidentally made the alien ships speed up as the player destroyed them. It wasn’t planned — the computer simply had fewer graphics to draw, so it processed everything faster! Players loved the challenge, so the “bug” became an official feature.

You’ve designed a blueprint, created characters, and built levels. But without programming, those characters are just statues. Let’s bring your world to life.

4.1 — Thinking Like a Computer

Computers aren’t smart — they’re just fast and obedient. A computer only does exactly what you tell it. To make a game, you need to break big actions into tiny, logical steps.

If/Then/Else

The foundation of all programming is the if/then statement — it tells the computer what to do when something happens:

IF the player presses Jump → THEN move the character up

Games are usually more complex, so we add an Else branch. Think of Super Mario:

IF Mario gets hit AND has a Super Mushroom → THEN he shrinks
ELSE → he loses a life

Booleans

A Boolean is a simple True or False value. Think of a zombie in Minecraft:

Condition	Result
`isDaytime = True`	Zombie catches fire 🔥
`isDaytime = False`	Zombie keeps chasing you 🧟

You can combine Booleans with AND / OR operators to make more complex decisions.

Flowcharts and Loops

Before writing code, developers often draw a flowchart to plan their logic visually.

When you need an action to repeat, you use loop:

Loop Type	What It Does	Example
While Loop	Runs while a condition is true	While health > 0, keep playing battle music
For Loop	Runs a specific number of times	Run this code 5 times to spawn 5 enemies

Functions

A function is a mini-program you write once and reuse whenever you want. Instead of typing the same damage math 100 times, you write a CalculateDamage function once and call it whenever needed.

4.2 — Keeping Track of the Game

While your game runs, the computer needs to remember a ton of information. That’s where data storage comes in.

Variables and Constants

Concept	What It Is	Example
variable	A box that stores info that can change	`playerHealth = 100`
constant	A locked box that never changes	`MAX_LEVEL = 100`

Primitive Data Types

When you create these storage boxes, you choose a data type:

Integers — Whole numbers. Perfect for counting: 5 coins, 3 lives, 1 sword.
Floats — Numbers with decimals. Great for precision: a movement speed of 4.5.
Strings — Words and text. When an NPC says "Welcome to my shop!", that’s a String.

Arrays

An array stores many similar items in a numbered list instead of creating hundreds of separate variables.

Object-Oriented Programming (OOP)

Professionals use Object-Oriented Programming to stay organized. Think of it like a cookie cutter:

Design one Goomba Class (the cookie cutter) with variables for health and speed.
Stamp out 50 Goomba Objects into your game — each one independent.

4.3 — Making Things Move and React

The Game Loop

Behind the scenes, the game loop runs over and over — usually 60 times per second (60 FPS). Every cycle, it checks:

Did the player press a button?
Where is everything now?
Should we play a sound?

Input

You write code that responds to two kinds of input:

Hardware input — keyboard, mouse, joystick
GUI input — clicking an on-screen button like “Inventory”

Collision Detection

The game needs to know when objects bump into each other. Every character has a hitbox — an invisible box drawn around them. When two hitboxes overlap, a collision happens, and your code decides what to do next.

Point Systems and Feedback

To make gameplay rewarding, implement a feedback loop. Display the score on the GUI and trigger a satisfying sound effect every time it increases!

4.4 — Code Types and Catching Mistakes

Visual vs. Scripting

Modern game engines offer two approaches:

Approach	How It Works	Examples
Visual Programming	Drag-and-drop blocks	Scratch, Unreal Blueprints
Scripting	Typing code line by line	C# in Unity, Lua in Roblox Studio

Syntax vs. Semantics

Term	Meaning	Analogy
syntax	The spelling & grammar of your code	Like following English grammar rules
semantics	The actual meaning of your instructions	Like whether your sentence makes sense

Errors and Debugging

Mistakes will happen. Here are the two main types:

Compile error — Stops the game from even starting. Usually a syntax mistake.
Runtime error — Happens while you’re playing. The code runs, but something goes wrong.

To fix bugs, you debug.