Your starting point
You can run a small project and understand a few variables and event handlers. Begin with simple shapes and one room.
- Basic variables, conditions, and functions.
- A local game or browser setup you can run with assistance.
Your finish line
You can build and verify a small round, separate input from gameplay rules, and explain the different control and lifecycle checks needed for browser, mobile, and PC play.
Stack up four small wins
Starting marks your intent to follow the path. Check off steps as you learn.
STEP 1 OF 4
Describe a round you can finish
Write a four-sentence description of a player moving in a room, collecting three stars, winning, and restarting. Identify what must reset and which state is temporary.
Bro tip: List the player position, stars, score, and round state that restart must restore. Use that list as your first playthrough checklist.
What you’ll learn
- Player action and game rule
- Win, failure, pause, and restart states
- Simulation updates versus rendered frames
You’re ready to move on whenThe description gives an observable win condition and a complete list of round state that restart must restore.
Your round has a finish line now. That is a solid place to start, bro.
STEP 2 OF 4
Finish one browser game journey
Complete the Browser Star Collector Starter using simple assets. Review the complete round before adding a hazard or larger level.
Bro tip: After winning, restart twice and revisit an old star location. Watch for extra score or a collectible that forgot to return.
What you’ll learn
- Movement boundaries
- Collection exactly once
- Game state and restart
You’re ready to move on whenYou can collect three stars, win, and restart twice without extra score or missing collectibles.
Open project: Browser Star Collector Starter
Round checkpoint marked. Keep that win-and-restart journey as your quick playtest.
STEP 3 OF 4
Adapt controls to simultaneous touch
Complete the Mobile Touch Dodge Practice. Use a simulator for layout and an actual touch device when available, recording the difference in evidence.
Bro tip: Try moving with one finger while acting with another, then interrupt the game. Note which checks used a simulator and which used a touch device.
What you’ll learn
- Independent contacts
- Touch cancellation
- Interruption and narrow-screen layout
You’re ready to move on whenMoving and acting together works, releasing a contact clears its action, and returning from interruption does not leave movement stuck.
Open project: Mobile Touch Dodge Practice
Nice, bro. You have marked the touch checkpoint with interruption behavior in mind.
STEP 4 OF 4
Add deliberate PC input preferences
Complete the PC Arena Controls Prototype. Keep the arena small while checking mappings, defaults, and preference restoration.
Bro tip: Remap one action and compare its behavior with the displayed instruction. Reopen settings after restart before adding more arena features.
What you’ll learn
- Named actions and remapping
- Instruction labels
- Focus loss and local settings
You’re ready to move on whenA remapped action changes both behavior and displayed instruction, defaults restore usable controls, and preferences survive restart.
Open project: PC Arena Controls Prototype
Your PC controls checkpoint is marked. Clear instructions deserve a small victory lap.
Your build lineup
- Browser Star Collector Starter
Build a tiny game with movement, collectibles, a win state, and a repeatable restart.
- Mobile Touch Dodge Practice
Adapt a small arena to touch controls that survive multiple fingers and interruptions.
- PC Arena Controls Prototype
Practice keyboard and gamepad action mappings, settings, and persistent preferences in a tiny arena.
Watch it. Then build it.
Start with a worked example, then connect the recording to your own small, checkable build. Videos open on their creator’s or publisher’s website.
Read Vibe Bro’s written lesson briefing ↗
Beginner · Video
How to make a Video Game - Godot Beginner Tutorial
Brackeys
See how an engine project turns scenes, movement, collisions, and feedback into a small playable game.
For step 1: Describe a round you can finish
Before watching: No previous Godot experience required. Stack: Godot and GDScript; basic variables and functions help when following the scripts.
Watch, then tryIdentify the player action, the game rule, and the feedback for one interaction. Rebuild one tiny mechanic before adding more level content.
This is an engine-based option alongside the browser route below. Follow the recording's Godot version when reproducing it, then consult current docs for changed editor controls.
Publisher’s course details · checked October 28, 2026
Next step · Video course · About 5 hours
Learn JavaScript by Building 7 Games - Full Course
freeCodeCamp · Ania Kubów
Build browser games while practicing events, collections, visible state, and simple game rules.
For step 2: Finish one browser game journey
Before watching: Basic HTML, CSS, and JavaScript variables and functions. Stack: browser JavaScript; no game engine is required.
Watch, then tryBegin with one short game. Name its state and win condition, then apply the same input–rule–feedback structure to the Star Collector.
Pick the browser route if the project uses JavaScript. The course games differ from our starter, so use its mechanics as examples and verify our own restart and collection rules.
Watch course ↗ · Practice: Browser Star Collector Starter
Publisher’s course details · checked October 28, 2026
Video links selected . Selection checks cover publisher metadata and topic fit.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- MDN — building a complete browser game
- Unity — on-screen sticks and controls
- Godot — input actions and event handling
Documentation links checked .
Editorial review · October 28, 2026
Qualified: Original four-step learning sequence and outcome, not a measured learner result. Project references resolve. Publisher metadata supports both game tutorial titles/creators/topics and the freeCodeCamp five-hour label; prerequisites and step placement are editorial guidance. Brackeys is explicitly an engine option, not the JavaScript project implementation. Recordings were not fully watched.