Module Six: Fundamentals of Game Development
Welcome, young creator! In this module, you will learn how video games are made. You will think like a game designer, plan like a builder, and create like an artist. Let’s begin our adventure into the world of game development!
Module Introduction
Have you ever played a game on a phone, a tablet, or a computer? Have you ever wondered, “How did they make this? How do the characters move? Why do I keep playing to beat the next level?” All of these things come from something called game development.
Game development means creating a game from just an idea. It is like baking a special cake. You need a recipe (that’s your plan), ingredients (like art and sound), and an oven (the computer program) to bake it. Once it’s ready, your friends can enjoy it!
This module will teach you the fundamentals of game development. Fundamentals are the basic, most important building blocks. If you understand these building blocks, you can create any game you dream of. We will avoid big, confusing words. Every new idea will be explained as if we are sitting under a tree, sharing stories. Ready? Let’s go!
Learning Objectives
By the time you finish this module, you will be able to:
- Say what game development means in your own words.
- List the three main parts of every game: input, update, and render.
- Explain what a game loop is and why it matters.
- Understand how a computer thinks about a game world using coordinates.
- Describe what a game engine helps us do.
- Know the difference between a sprite, an object, and a level.
- Create a simple game design on paper.
- Tell a story through a game.
- Work well with others to build a small game idea.
Warm-up Story: Kola and the Magic Chicken
Kola lived in a small town in Nigeria. He loved playing a game called “Jumping Chicks” on his mum’s phone. One day, the power went out. The phone was dead, and Kola was bored. He sat in his backyard, watching real chickens peck at corn.
Suddenly, Kola had an idea. He drew a grid on the ground with a stick. He picked up a stone. “This stone,” he said to his little sister, Amara, “is the Magic Chicken. It has to jump over these lines to reach the corn!” Amara giggled. Kola made rules: if you throw the stone and it lands on a line, the chicken falls. If it lands in the next box, you earn one kernel of corn.
Soon, his friends came over. They started adding new rules. One friend said, “What if there’s a hawk that flies in every three turns?” Another said, “What if the chicken can double-jump once per game?” Without a phone or a computer, Kola had become a game developer. He had an idea, he made rules, he built a playing area, and he saw if it was fun. This is exactly how big games like “Angry Birds” or “Subway Surfers” begin—with a simple idea and clear rules. Kola’s dirt grid was his screen, the stone was his character, and his friends were his players. You, too, can start just like Kola.
Main Lessons
Lesson 1: What Is a Game Developer?
Definition: A game developer is someone who makes a game. They use computers, but they also use their imagination, logic, and art.
Why it is important: Knowing who a developer is helps you see that YOU can become one.
Simple explanation: Think of a game developer as a chef. The chef follows a recipe (code) and mixes ingredients (art, sound, story) to serve a meal (the game). A developer can be one person doing all the cooking, or a big team where one person just chops vegetables (makes sounds) and another just bakes the bread (writes code).
Real-life example: A carpenter builds a chair; a game developer builds a game world.
School example: When your teacher gives you a group project to draw a map of your school, you all become developers of that map. Someone draws, someone measures, someone writes the names.
Home example: When you arrange your room and make a rule that “the floor is lava,” you have developed a game!
Nigerian example: Imagine a Nigerian team like Kuluya Games or ChopUp Games. The people there are developers. They create games about African history, like a game where you run a busy Lagos market.
Illustration:
Game Developer
|
+-----+------+
| |
Uses Brain Uses Tools
(Imagination) (Computer)
| |
Makes Rules Builds World
|
The Game 🎮
Mini Summary: A game developer is anyone who creates a game by making rules and building a world. You can be a developer right now with just paper and a pencil.
Lesson 2: The Three Magic Words – Input, Update, Render
Definition: Every game, from a simple tic-tac-toe to a complex racing game, does three things in a circle: Input (listen to the player), Update (change the game state), and Render (draw the new picture).
Why it is important: This is the heartbeat of a game. If you understand this circle, you understand how all digital games work.
Simple explanation: Imagine you are drawing a flip-book. You draw a stick man on page one. On page two, you draw him with his arm a little higher. When you flip the pages fast, the stick man waves. Here, Input is your decision to flip the page. Update is the arm changing position. Render is your eye seeing the new picture. The game repeats this very fast.
Real-life example: A traffic light. Input: A car waits. Update: The timer changes the light from red to green. Render: The green light shines. Drivers see it.
School example: In a spelling bee. Input: The teacher says a word. Update: Your brain thinks of the letters. Render: You speak the spelling aloud.
Home example: The “floor is lava” game. Input: Mum shouts “Lava!” Update: Everyone must jump on a pillow. Render: You see your brother climbing the sofa.
Nigerian example: Playing the “Ayo” board game. Input: You pick up seeds from a hole. Update: You drop one seed in each next hole according to the rules. Render: You and your opponent see the new positions of all seeds.
Illustration:
+--------+
| INPUT | <--- Player presses a key or touches screen
+--------+
|
v
+--------+
| UPDATE | <--- The game logic moves the character, checks rules
+--------+
|
v
+--------+
| RENDER | <--- The screen shows the new picture
+--------+
|
+----> (Repeat! This is the Game Loop)
Mini Summary: Games take input, update the action, and render the new frame. This loop happens many times per second.
Lesson 3: The Game Loop – The Spinning Wheel
Definition: The Game Loop is a repeating cycle that keeps the game running until the player wins or loses. It spins like a bicycle wheel, over and over.
Why it is important: Without a loop, a game would just freeze after the first move. The loop keeps the game alive!
Simple explanation: Picture a roundabout (merry-go-round) in a playground. You push it (input). It spins (update). You see your friends whizzing past (render). It keeps spinning as long as someone pushes it. The game loop is the spinning. It spins, checks if something new happened, draws the scene, and spins again. It spins so fast—maybe 30 or 60 times in a single second—that it looks like smooth movement.
Real-life example: Your heartbeat. It goes beat… beat… beat. Each beat sends blood around. It does not stop until you rest. A game loop does not stop until you close the game.
School example: The school bell system. The loop: ring bell (update period), students move (render), teachers teach (input), wait for next ring. Repeat daily.
Home example: Washing machine. It fills water, washes, drains, spins. It loops through these steps until the timer ends.
Nigerian example: A danfo bus (Lagos yellow bus) conductor’s call loop. He shouts “Oshodi! Oshodi!” (input/marketing), waits for passengers (update), collects fare (input), and when bus fills, driver moves (render). The shout cycle repeats.
Illustration:
Start Game
|
v
+--> Check if player pressed something (Input)
| |
| v
| Move character, update score (Update)
| |
| v
| Draw everything on screen (Render)
| |
+-------+
(keep going until Game Over)
Mini Summary: The game loop is a fast, never-ending circle of input, update, and render. It is the engine that drives every single game.
Lesson 4: Thinking with Coordinates – X and Y
Definition: A coordinate is a pair of numbers (X, Y) that tells the computer exactly where something is on the screen. X is how far right; Y is how far down.
Why it is important: A computer screen has millions of tiny dots called pixels. To place a character, the game must use coordinates. Without them, the computer cannot find the spot.
Simple explanation: Think of a giant classroom window with square panes. You want to place a sticker of a butterfly. You tell your friend, “Start from the left side, count 3 panes to the right (that’s X). Then count 2 panes down from the top (that’s Y).” The butterfly goes exactly there. In games, the top-left corner is often (0,0).
Real-life example: A map grid in a street directory. To find a shop, you might look at grid reference B5. B is the X direction, 5 is the Y direction.
School example: Your seat in class. “Row 4, desk 3” is a coordinate. The teacher can find you without calling your name.
Home example: A chessboard or a checkers board. The rook is on column D, row 1. That is its coordinate (D,1).
Nigerian example: In the game “Whot,” you lay out cards in rows and columns. The position of the “Star” card on the mat is like a coordinate. In a local market, a trader says, “My stall is Block 2, Row A.” That’s a coordinate!
Illustration:
(0,0) ----> X increases right
|
| * (3,2) <-- The star is 3 steps right, 2 steps down
|
v
Y increases down
Mini Summary: Coordinates (X, Y) are the address of a pixel on the screen. X is across, Y is down. Games move things by changing these numbers.
Lesson 5: Sprites – The Game Actors
Definition: A sprite (pronounced like “spright”) is a 2D picture or image that moves around in a game. Characters, coins, bullets, and trees are often sprites.
Why it is important: Sprites are the actors in your game movie. Everything you see moving is usually a sprite.
Simple explanation: Imagine you cut out a paper doll. You can slide it across a background picture. The paper doll is the sprite. The background is the game stage. In a digital game, the sprite is just a rectangle filled with a drawing, and the computer moves that rectangle by changing its X and Y coordinates.
Real-life example: A cartoon animation cell. Old cartoons painted characters on clear plastic sheets and moved them over a painted background.
School example: A magnet of a bee on the classroom whiteboard. The bee is the sprite; the whiteboard is the background.
Home example: A sticker on your notebook. You can peel it off and put it somewhere else on the cover.
Nigerian example: During the Argungu Fishing Festival, a fish jumping out of the water could be a sprite. The river is the background. In a local game, a carved wooden figure (like an ayo seed) moving on a board acts like a sprite.
Illustration:
+------+
| /\ |
| (..) | <-- This is a Sprite (an owl)
| /\/\ |
+------+
|
v (X: 100, Y: 50) <-- Its position on screen
Mini Summary: A sprite is a movable picture. By changing its coordinate, we make it walk, fly, or jump.
Lesson 6: Collision Detection – Did They Touch?
Definition: Collision detection is how a game knows when two sprites touch each other. For example, when a player touches a coin or an enemy.
Why it is important: If a game cannot tell when things touch, you could walk through walls, or a bullet would never hit a target. It is the sense of touch for the game world.
Simple explanation: Imagine two soap bubbles floating in the air. When the bubbles meet, they pop or join. The game checks, “Is the edge of bubble one inside bubble two?” It does this using coordinates and the shapes. Most beginners use a simple rectangle check: if two rectangles overlap, they touch!
Real-life example: Two people walking towards each other in a doorway. If both try to pass, their shoulders might bump. The bump is a collision.
School example: In a school play, when two actors stand very close, the audience believes they are talking to each other. The director checks, “Are they close enough to each other?”
Home example: Playing a game of tag. Your hand touches someone’s back. The game rule says that touch means “you’re it.”
Nigerian example: In a crowded Lagos bus stop, you know you’ve “collided” with another passenger when your shoulder touches theirs. A game designer would say, “If PlayerX < PassengerX + width, then collision!”
Illustration:
[Player] [Coin]
| |
+---> X <---+
(Overlap!)
YES = Collect Coin
NO = Keep Moving
Mini Summary: Collision detection answers the question, “Are these two game objects touching?” It decides if you eat the fruit, kill the monster, or win the race.
Lesson 7: Game Physics – Making Things Feel Real
Definition: Game physics are the rules that make things move in ways that feel like the real world. Gravity is the most famous one. Things fall, bounce, or slide based on game physics.
Why it is important: Without physics, a character would float away or stop suddenly without slowing. Physics makes the world feel solid and believable.
Simple explanation: You know that if you drop a ball, it goes down. In a game, you tell the computer, “Every second, increase the downward speed of the ball until it hits the ground.” That’s gravity code. To jump, you give the character a sudden burst of upward speed. Gravity then pulls it back down naturally.
Real-life example: A swing at a park. You pump your legs to go up (force). Gravity pulls you back down. You keep swinging until friction and air slow you down.
School example: A paper plane. You throw it hard, but air pushes back. Gravity pulls it down. It glides. That’s physics.
Home example: A bouncing ball in your room. Drop it; it hits the floor (collision detection) and bounces back (physics reaction).
Nigerian example: Throwing a bouncy ball (like a rubber “bouncy” from a shop) on a dusty ground in a village square. It might not bounce as high because the sand absorbs energy. A game can copy that!
Illustration:
Jump:
Player Y speed = -10 (Up)
|
v (Gravity pulls down: add +1 speed every tick)
Player Y speed = -9, -8, ..., 0
|
v
Player Y speed = +1, +2, ... (Falling down)
Bounce!
Mini Summary: Game physics uses simple math to fake real forces like gravity. It makes jumping and bouncing look correct.
Lesson 8: Game Engines – The Tool Factory
Definition: A game engine is a box of ready-made tools that helps developers build games faster. It handles the game loop, physics, sound, and graphics for you.
Why it is important: Building a game without an engine is like baking a cake without an oven, mixer, or spoons. You could do it with bare hands, but it’s very hard. Engines give you the tools.
Simple explanation: Imagine you love making cookies. A game engine is like a modern kitchen. It has a timer (loop), a mixer (input handler), and an oven (renderer). You still need to make the dough and design the cookie shape (that’s your game idea), but the kitchen makes the job possible and fun.
Real-life example: A car factory. Robots and conveyor belts help workers. Workers don’t have to carry heavy metal by hand; the factory engine helps.
School example: A pre-printed science project template. The lines and structure are given; you just fill in the experiment details.
Home example: A Lego set comes with bricks and instructions. The set doesn’t build the castle for you, but it gives you the parts.
Nigerian example: Think of a popular engine like Unity or Godot. Some Nigerian developers use Buildbox or GameMaker to make mobile games without writing too much complex code. It’s like using a motorized grinding machine instead of a stone grinder—faster and easier.
Mini Summary: A game engine is a helper program that does the hard, boring work so you can focus on making your game fun.
Lesson 9: Levels and World Design
Definition: A level is one part or stage of a game. World design is how you arrange platforms, enemies, and treasures in that level to tell a story or give a challenge.
Why it is important: A good level makes a player feel smart, excited, or brave. A bad level makes them feel bored or unfairly treated.
Simple explanation: You are building an obstacle course for your pet or a friend. You place a tunnel, then a jump over water, then a narrow beam. You decide the order. You want it to start easy, then get harder. The order of obstacles is the “level design.”
Real-life example: A playground. The designer placed the slide after the climbing net, and the swings next to the sandpit. They designed the “play level.”
School example: The layout of your classroom. The teacher’s desk is at the front (the boss), the bookshelf is at the back (treasure), and tables are in rows (safe paths).
Home example: A family board game like Ludo. The path from start to home is a level. The safe spots and star spots are designed to make it tricky but fun.
Nigerian example: The layout of a traditional wrestling match in a village. The circle is the ring (level boundary). The rules say you must push your opponent out. The level design is just the circle, but it creates the whole game dynamic.
Illustration:
Level 1 (Garden):
[Start] ----> [Jump over log] ----> [Collect Mango] ----> [Finish]
Easy Medium Safe Goal
Mini Summary: Level design is arranging the pieces of your game to create a fun path for the player. It is like writing a song with ups and downs.
Lesson 10: Sound and Music – The Feeling Makers
Definition: Sound effects are short noises (like a “boing” for a jump or a “clink” for a coin). Music is the background song that plays during a level.
Why it is important: Sound tells your ears what your eyes might miss. It warns you of danger or rewards you. It makes the game feel alive.
Simple explanation: Watch a cartoon with the volume off. It looks fine but feels empty. Now turn the volume up. The silly sounds make you laugh. Music tells you “this is a scary part” or “this is a happy part.” Games are the same.
Real-life example: A doorbell. The ring is a sound effect that says, “Someone is here.”
School example: The school bell is the sound effect for “class change.” The songs you sing in assembly are like the soundtrack.
Home example: The beep of a microwave. It tells you your food is ready without you looking.
Nigerian example: Imagine a game about a talking drum festival. The player hears actual talking drum beats when they get a correct rhythm. It teaches culture through sound effects!
Mini Summary: Sound and music add emotion and information. A “swoosh” makes a punch feel powerful; a lullaby makes a night level feel calm.
Lesson 11: The Game Design Document (GDD)
Definition: A Game Design Document is a written plan on paper. It describes everything about your game before you start coding: the hero, the goal, the rules, the levels.
Why it is important: Building a house without a blueprint is dangerous. Building a game without a plan is confusing. The GDD keeps you on track.
Simple explanation: Before Kola drew the grid for his Magic Chicken game, he had a plan in his head. A GDD is putting that plan on paper so your teammates can read it and help.
Real-life example: A recipe book. It lists the name of the dish, a picture, the ingredients list, and the steps.
School example: A project report outline. You write the title, the objectives, and the steps before you start writing.
Home example: A shopping list. It prevents you from buying things you don’t need and forgetting important ones.
Nigerian example: A Nigerian architect building a house in Abuja first draws the plan. A Nigerian game developer writing a GDD first sketches the character (maybe a little girl carrying a calabash) and the mission.
Illustration:
+-----------------------------+
| GAME DESIGN DOCUMENT |
|-----------------------------|
| Title: Magic Chicken Chase |
| Hero: Stone |
| Goal: Reach the corn |
| Rules: Avoid lines |
| Levels: Yard, Field, Market |
+-----------------------------+
Mini Summary: A GDD is your game’s master plan. Write it down so you don’t forget your amazing ideas.
Lesson 12: Art and Animation – Making It Move
Definition: Game art is the drawings. Animation is making those drawings move like a cartoon. A running character is actually a few pictures shown very fast.
Why it is important: Art attracts players. Animation makes the world convincing. A stiff character feels like a robot; an animated one feels like a friend.
Simple explanation: Take a sticky note pad. Draw a ball on the bottom right on the first page. On the next page, draw it a little to the left. Flip the pages fast. The ball moves! A game animates sprites by quickly changing from one picture (sprite frame) to another.
Real-life example: A traffic light’s walking man symbol. Some new ones have a countdown that animates the man walking faster.
School example: Flip books you make in your notebook. A stickman doing a backflip is animation.
Home example: A zoetrope spinning drum. You look through the slits and see a horse galloping.
Nigerian example: Nollywood movies with special effects sometimes use simple animations. In a game, you could animate a character wearing traditional agbada flapping in the wind as he runs.
Mini Summary: Animation is showing a series of pictures quickly to trick the eye into seeing motion. It makes your sprites walk, dance, or jump.
Lesson 13: Testing – Finding the Bugs
Definition: Testing is playing your game to find problems (bugs) before your friends play it. A bug is a mistake or a glitch.
Why it is important: If you don’t test, players might fall through the floor or get stuck. Testing makes sure the game is fair and fun.
Simple explanation: You write a story and read it aloud. You might find a word spelled wrong or a sentence that sounds silly. Testing a game is the same: you play to see if anything acts weird.
Real-life example: A baker tastes the soup before serving it to guests. They check if it needs more salt.
School example: Checking your math homework answers with a calculator or a friend before submitting it.
Home example: Before a big party, you check the decorations to see if any balloons have popped.
Nigerian example: A local mechanic in a repair shop tests an engine by listening to it before the customer picks up the car. He is “testing the build.”
Mini Summary: Testing is playing your own game with a detective’s eyes. Find bugs, fix them, and make the game perfect.
Lesson 14: Publishing and Sharing Your Game
Definition: Publishing is putting your finished game in a place where others can download and play it—like an app store or a website.
Why it is important: A game is meant to be played! Sharing it makes you a real developer. Getting feedback makes your next game better.
Simple explanation: You bake a cake and keep it in the kitchen. Publishing is putting the cake on the dining table and calling everyone to eat.
Real-life example: An author writes a book. Publishing is printing it and putting it in a library or bookshop.
School example: Putting your art project on the classroom wall for everyone to see during Parents’ Day.
Home example: Sharing a video of your family’s dance on a family WhatsApp group.
Nigerian example: A Nigerian developer can publish a game on the Google Play Store. Popular Nigerian games like “Okada Ride” were published for all the world to download and enjoy.
Mini Summary: Publishing means sharing your game with players. Their smiles and feedback are your reward.
Lesson 15: Teamwork – Nobody Builds a Big Game Alone
Definition: Teamwork is working together. Big games need artists, programmers, sound designers, and testers all working as one team.
Why it is important: One person can make a small game, but huge games need many brains and hands. Sharing ideas makes the game richer.
Simple explanation: A football team. The goalkeeper cannot also be the striker all the time. Each person has a job. When they pass the ball to each other, they win. A game team passes tasks: “You draw the monster, I’ll code its health, she will make its roar sound.”
Real-life example: Building a real house. A bricklayer, an electrician, and a painter work together. None of them builds the whole house alone.
School example: A group debate. One person researches, one writes, one speaks.
Home example: Preparing a big Sunday meal. Mum cooks the stew, you wash the plates, sister pounds the yam.
Nigerian example: In a Nigerian film set, there is the director, cameraman, actors, and makeup artist. Game development works exactly like this crew. Everyone does their part to make the final product great.
Mini Summary: Game development is a team sport. Using everyone’s talent makes the game bigger and more fun.
Key Vocabulary
| Word | Simple Definition |
|---|---|
| Game Developer | A person who makes a game. |
| Input | What the player does (press a key, touch the screen). |
| Update | The game rules that change the action. |
| Render | Drawing the new scene on the screen. |
| Game Loop | The repeating circle of Input, Update, Render. |
| Coordinate | An address on the screen (X, Y). |
| Sprite | A 2D image that moves. |
| Collision | When two sprites touch. |
| Physics | Rules for movement like gravity. |
| Game Engine | A toolbox for building games. |
| Level | One stage of the game. |
| GDD | Game Design Document, the written plan. |
| Animation | Showing pictures quickly to make them look alive. |
| Bug | A mistake or error in the game. |
| Publish | Share your game for others to play. |
Important Concepts
The Golden Circle: Input ➜ Update ➜ Render. This is the most important concept in this module. It is the DNA of a game.
Everything is a Number: The computer sees positions as numbers (coordinates), speeds as numbers (physics), and images as numbers (pixels). Good game developers learn to think in numbers.
Plan First, Code Second: Professionals almost always write a GDD before they type a single line of code. A plan saves hours of pain.
Step-by-Step Explanations: Making a Simple Click-the-Bird Game
Let’s imagine how the game loop works in a simple bird-tapping game.
- Wait for Input: The game is drawn on the screen. The bird sprite sits at coordinate (200, 100). You touch the screen.
- Check Collision: Did your finger’s coordinate touch the bird’s rectangle? Yes!
- Update World: Increase the score by 1. Move the bird to a new random coordinate, say (350, 200). Play a “chirp” sound.
- Render: Clear the screen. Draw the sky. Draw the bird at the new spot. Draw the new score.
- Loop Again: Wait for the next tap. Keep doing this until the timer runs out.
Tap Screen (Input)
|
v
Is Bird Touched? (Collision Check)
|
YES |---> Score +1, Move Bird, Play Chirp (Update)
|
v
Draw All (Render)
|
v
(Repeat)
Real-life Examples of Game Development Concepts
- A restaurant menu is like a game level: you choose a path from appetizers to dessert.
- A traffic warden directing cars acts like a game loop checking for input and updating flow.
- A goalkeeper diving for a ball is collision detection: the ball (sprite) touches the glove (sprite).
- A barber’s price list is a GDD: it tells you the services and rules.
Nigerian Examples
- Ayo Olopon: A traditional strategy game. The board holes are coordinates. The seeds are sprites. Capturing seeds uses collision detection.
- Abula (Amala, Ewedu, Gbegiri): Making this dish is like assembling a game. You need multiple parts (soup, swallow, stew) that must come together perfectly. Game assets (art, sound, code) also must come together.
- Lagos Market: Navigating a crowded market without bumping into people is a live-action game of collision avoidance.
Fun Examples
- Hide and Seek: The “renderer” is your eyes. The “update” is you counting down and everyone running. The “input” is hearing “Ready or not, here I come!”
- Building a Pillow Fort: The fort is your level design. The cushions are physics objects.
- Simon Says: Simon is the input. Your body does the update. Your friends watching is the render.
Everyday Examples
- A microwave has a loop: input (buttons), update (cook time), render (display numbers).
- Brushing your teeth: input (squeeze paste), update (brush up and down), render (clean teeth smile).
Teacher Notes
This module is designed to demystify game creation. Emphasize that no computer is needed to start thinking like a developer. Use the outdoor “Kola Grid” activity. Encourage students to draw their game screens on paper first. The key hurdle is the coordinate system; use a large floor grid with masking tape to let students physically walk to (X, Y) coordinates. Reinforce the Input-Update-Render loop with physical clapping games.
Parent Tips
Celebrate your child’s interest in games by asking them to describe the “rules” of their favorite game instead of just playing it. Ask, “Why do you think the designer made the coin that color?” or “What would you change?” Download a free child-friendly engine like Scratch (visual coding) and build the click-the-bird game together. Validate that playing games can be educational when done with curiosity.
Interesting Facts
- The first video game ever is often called Pong (1972). It was just two white rectangles and a dot.
- Mario from Super Mario is a sprite who got his mustache because the first game screens couldn’t show a mouth clearly.
- There is a game developer in Nigeria who made a game called “Danfo Driver” based on driving the yellow buses in Lagos.
- Some of the best game ideas ever sold were written on a paper napkin first.
Did You Know?
Did you know that the sound of a thunderstorm in a game can be made by shaking a large sheet of metal? Sound designers are creative chefs of noise!
Did you know that in a flight simulator game, the clouds are often just painted half-spheres (sprites) that rotate to face you? This is a trick called “billboarding.”
Remember This
- Games are just rules plus art plus sound.
- If you can imagine it, you can plan it.
- Every big game starts with a tiny idea.
- “Input, Update, Render” is the heartbeat.
- Bugs are not bad animals; they are just mistakes to fix.
Common Mistakes
- Starting too big: Wanting to build a 3D open-world RPG as your first game. Start with a single room or a click game.
- Forgetting the GDD: Coding without a plan leads to “what was I doing?” confusion.
- Skipping testing: Only testing the first level yourself. Let your little brother play; he will break it in ways you never imagined.
Best Practices
- Make a paper prototype first. Cut out sprites from paper and slide them on a background drawing.
- Make the core loop fun before adding fancy art. A grey box that jumps nicely is better than a beautiful dragon that can’t move.
- Save your work. Copy your project folder every day. Call it “MyGame_Monday,” “MyGame_Tuesday,” etc.
- Ask for feedback. “Is this fun?” is the most important question.
More Visual Aids
Flowchart: Choosing a Game Idea
Start
|
v
Do you like racing?
/ \
YES NO
/ \
Make a Do you like jumping?
Car Race / \
YES NO
/ \
Platformer Make a Puzzle Game
Timeline: Game Development Path
Day 1: Idea & GDD
Day 2: Draw Sprites on Paper
Day 3: Build First Level in Editor
Day 4: Add Physics & Movement
Day 5: Add Sounds
Day 6: Test and Fix Bugs
Day 7: Publish and Celebrate! 🎉
Table: Input Methods
| Device | Input Method | Game Example |
|---|---|---|
| Phone | Touch Screen | Angry Birds |
| Computer | Keyboard & Mouse | Roblox |
| Console | Gamepad | FIFA |
| Wii/Switch | Motion control | Just Dance |
Comparison: 2D Game vs 3D Game
| Feature | 2D Game | 3D Game |
|---|---|---|
| Movement | Only X (left/right) and Y (up/down) | Adds Z (near/far) |
| Graphics | Flat drawings (Sprites) | Models with depth (like clay statues) |
| Camera | Usually fixed side-view or top-down | Can rotate all around |
| Example | Super Mario Bros, Ayo digital | Minecraft, Temple Run |
| Easier for beginners? | Yes! | Takes more practice |
End-of-Module Summary
Wow! You have finished Module Six. You are no longer just a game player; you are a game thinker. Let’s recap the journey:
- We met Kola, who built a game in the dirt with a stone and a stick.
- We learned that games run on a magic circle: Input, Update, and Render. This circle spins in the Game Loop.
- We found out that screens use coordinates (X, Y) to place our sprites, just like finding a seat in a cinema.
- We made sure characters don’t walk through walls with Collision Detection.
- We added Physics so things bounce and fall like real life.
- We used Game Engines as our toolbox and wrote a GDD to plan before building.
- We designed Levels, added Sound, Animated our sprites, and Tested like a detective.
- Finally, we learned to Publish and work as a Team.
Remember, the best game in the world started as a simple idea someone wrote down. You have the tools, you have the imagination, and you have the power to create. Game development is fun with a plan!
Frequently Asked Questions (FAQs)
- Q: Do I have to be good at math to make games?
A: Not really! Basic addition and subtraction are enough to start. The computer does the hard math. - Q: Can I make a game without a computer?
A: Yes! You can design board games, card games, or even active games like Kola did. Paper prototypes are a real part of game development. - Q: What is a glitch?
A: A glitch is a type of bug. It’s when the game does something strange, like a character’s arm stretching across the room. - Q: How old is the youngest game developer?
A: Some children as young as 7 or 8 have published simple games on app stores with help from tools like Scratch or Buildbox. - Q: What is an NPC?
A: NPC stands for Non-Player Character. It’s a game character you don’t control, like a shopkeeper or a quest giver. - Q: Why does my game look blurry on a big screen?
A: Because the game art (sprites) might be too small. Think of stretching a small sticker onto a big wall; it gets blurry. - Q: Is a game engine a game?
A: No. A game engine is like a toy factory. The toy is the actual game you play. - Q: What is the easiest game to make first?
A: A “click the target” game or a simple “dodge the falling objects” game. - Q: Can I use photos I took for my game?
A: Yes! Many games use real photos turned into sprites or backgrounds. - Q: How long does it take to make a big game like FIFA?
A: Big games take hundreds of people working for one or two years. Start small and patient.
Review Questions (15 Questions)
- What are the three main steps in a game loop?
- Explain what a sprite is to your friend using only food examples.
- Why do we use a GDD (Game Design Document)?
- If a screen coordinate is (0, 0), where is it usually located?
- What is the difference between a game developer and a game player?
- Name one Nigerian game example that involves counting or strategy.
- Why is collision detection important in a racing game?
- What happens if we skip the testing phase?
- Describe the “Update” part of the loop in a soccer game.
- What tool helps you build a game faster by giving you pre-made physics and rendering?
- Is a game loop slow or fast?
- Why did Kola draw a grid on the ground?
- What part of game development involves adding a roar sound to a lion?
- Can one person be an artist and a coder at the same time?
- What does “Publish” mean?
Fill-in-the-Blank Exercises
1. The repeating circle in a game is called the ________ Loop.
2. A movable image in a 2D game is a ________.
3. The X coordinate usually goes from left to ________.
4. When two sprites overlap, we call it a ________.
5. A written plan for a game is called a ________ Design Document.
6. The force that pulls a jumping character down is called ________.
7. A mistake in the game is lovingly called a ________.
8. ________ is the step where the screen is redrawn.
9. To get better, we ask for ________ from players.
10. A toolbox for game creators is a Game ________.
True or False Exercises
1. A game developer only writes code. False
2. Input means the game showing the picture. False
3. Coordinates are used to find positions on the screen. True
4. Sound effects make a game feel alive. True
5. A bug is a small insect that eats your computer. False
6. Physics makes things move in unrealistic ways on purpose. False
7. A Game Design Document is a storybook about pirates. False
8. You should test your game thoroughly. True
9. Y coordinate usually goes up from the bottom. False (Usually down from the top)
10. Teamwork is important only for big games. False
Multiple Choice Questions (15 Questions)
- What does a game developer do?
a) Only plays games
b) Creates games
c) Sells computers
Answer: b - Which of these is NOT a main part of the game loop?
a) Input
b) Download
c) Render
Answer: b - A sprite is best described as:
a) A fizzy drink
b) A 2D image that moves
c) A type of tree
Answer: b - Collision detection checks:
a) If the game is too loud
b) If two objects touch
c) If the player is tired
Answer: b - Gravity in a game helps with:
a) Making sounds louder
b) Pulling objects down
c) Changing colors
Answer: b - What is a GDD?
a) Game Doing Device
b) Game Design Document
c) Great Donut Dough
Answer: b - Testing is done to find:
a) Gold
b) Bugs
c) New players
Answer: b - An example of input is:
a) Drawing the monster
b) Pressing the spacebar
c) Increasing the score
Answer: b - What does Render mean?
a) To tear paper
b) To draw the game on screen
c) To cook food
Answer: b - Which tool helps you build games faster?
a) Game Engine
b) Game Paper
c) Game Eraser
Answer: a - In coordinates, what does the X usually stand for?
a) The down direction
b) The horizontal direction
c) The volume level
Answer: b - If your character falls through the floor, it is likely a:
a) Feature
b) Bug
c) Reward
Answer: b - Publishing a game means:
a) Hiding it in a drawer
b) Making it available for others
c) Erasing it
Answer: b - Ayo Olopon is an example of a:
a) 3D Action Game
b) Traditional Strategy Game
c) Racing Game
Answer: b - What is the first step in building a good game?
a) Designing the sound
b) Making a plan (GDD)
c) Publishing the app
Answer: b
Matching Exercises
Match the word to its meaning:
| Word | Match | Meaning |
|---|---|---|
| 1. Sprite | A | Toolbox for making games |
| 2. Bug | B | A movable picture |
| 3. Engine | C | A mistake in the game |
| 4. Update | D | Listening to the player |
| 5. Input | E | Changing the score and moving things |
Answers: 1-B, 2-C, 3-A, 4-E, 5-D
Short Answer Questions
- Describe the “Floor is Lava” game in terms of Input, Update, and Render.
- Why is a coordinate (0,0) often in the top-left corner?
- List three jobs a person might have in a game development team.
- Explain what would happen if a game had no collision detection.
- Write a simple Game Design Document idea for a fruit-catching game.
Scenario-based Exercises
- Scenario: Your character keeps walking through walls. What part of the game loop is broken? How do you fix it? (Answer: The collision detection in the Update phase is missing or broken. You need to add a check that stops the character’s X coordinate if it touches the wall.)
- Scenario: You want to build a game where an eagle flies over Abuja and drops feathers. Is this 2D or 3D? What sprites do you need? (Answer: It can be 2D or 3D, but 2D is easier. Sprites needed: Eagle, feather, Abuja landscape background.)
Group Activity: The Human Game Loop
Goal: Act out the game loop.
- Divide into three groups: Input, Update, Render.
- Pick a scenario: a student throwing a paper ball into a bin.
- “Input” student says when the throw happens.
- “Update” students calculate the arc and say if it goes in or misses.
- “Render” students draw the result on the board (ball in bin or ball on floor).
- Loop it ten times. See how fast you can do it without mistakes!
Individual Activity: Your Game Idea Poster
Take a large sheet of paper. Fold it into four parts.
- Part 1: Write the Title of your game.
- Part 2: Draw the Main Character (Sprite).
- Part 3: Draw the Game World (Level 1).
- Part 4: List the Rules and Controls.
Hang it on your wall. You just started your GDD!
Classroom Discussion Questions
- Can a game be fun even if it has no sound? Why or why not?
- Is winning the only way to have fun in a game? Think of a game where you like building more than winning.
- What real-life Nigerian street games could be turned into a video game?
- If you were a bug in a game, what funny thing would you make the character do?
Mini Project: The Cardboard Console
Build a “game console” out of cardboard. Cut a square hole for the screen. Draw a background on a long strip of paper. Draw a sprite on a lollipop stick. Slide the background strip behind the “screen” and move your sprite stick over it. You just built a mechanical game! Show it to your family.
Practical Assignment: The Jump Calculation
Stand against a wall. Mark how high you can reach on the wall while standing flat-footed (this is your starting coordinate Y). Now jump and touch the wall as high as you can (this is your negative Y burst). Did gravity bring you down fast or slow? Draw a chart of your height changing over time.
Height
^
| *
| / \
| / \
| / \
|/ * (back to ground)
+-----------> Time
Challenge Exercise: The Invisible Maze
Design a maze on a grid (5x5). Write the coordinate path of the solution. For example: (0,0) ➜ (1,0) ➜ (2,0) ➜ (2,1) … up to (4,4). Give the list of coordinates (and only the list) to a partner. Can they trace the path on a blank grid without seeing the walls? You just sent “game data” like a computer does.
Quiz Answers (Quick Reference)
Fill-in-the-Blanks: 1.Game, 2.Sprite, 3.right, 4.Collision, 5.Game, 6.Gravity, 7.Bug, 8.Render, 9.Feedback, 10.Engine.
True/False: 1.F, 2.F, 3.T, 4.T, 5.F, 6.F, 7.F, 8.T, 9.F, 10.F.
MCQ Answers: See the answer key under each question (all B options).
Key Takeaways
- You are a creator. You don’t just consume games; you can build them.
- Simplicity is powerful. Kola’s stick and dirt were enough.
- Plan your work, work your plan. The GDD is your map.
- Math is your friend. Coordinates and speed use only simple numbers.
- Fun is the final goal. If the player smiles, you have succeeded.
Preparation for the Next Module: Module Seven – Introduction to Coding with Blocks
In Module Six, you learned the theory of how games work. You planned, designed, and thought like a developer. In the next module, we will bring these ideas to life using code!
But don’t worry—we won’t type scary text. We will use colorful blocks that snap together like toy bricks. This is called block coding (like in Scratch or MakeCode). You will move a sprite using real coordinates and build a game loop that actually runs on a screen.
To prepare for Module Seven, please do this:
- Think about the GDD poster you made. Which character will you want to code first?
- Practice writing down sequences of steps for daily activities. For example, write the exact “algorithm” for brushing your teeth. You will discover that the computer needs every tiny instruction, just like your list.
- If you have access to a computer, ask an adult to help you open Scratch. Look at the colorful blocks and see if you can find the “move 10 steps” block.
Get ready to turn your paper dreams into digital reality. You are about to become a coding wizard! See you in Module Seven.
End of Module Six. Great work, smart creator!