Remaking a Classic Arcade Game as Your Second Project
Our first original game took eleven weeks and was never finished. Our second project was a Breakout remake, and it was playable in four evenings. Nothing about our skills changed between the two.

Our first original game took eleven weeks and was never finished. Our second project was a Breakout remake, and it was playable in four evenings. Nothing about our skills changed between the two. What changed was that every design question already had an answer, so all our time went into actually building.
Remaking a classic arcade game is the project I now recommend to anyone who has finished one tiny game and wants to get better fast. You skip the hardest part of game development, deciding what the game should be, and practice the part that makes you a developer: turning a clear design into working code, art and sound. Here is how we pick a game to remake, how we scope it, and how we make it ours by the end.
Why Remaking a Classic Arcade Game Teaches More
When you design from scratch, every problem is two problems. Is the jump too floaty because of your code, or because the idea is wrong? With a remake, the target is known. If your Pong ball feels sluggish, you can open the original, compare, and know the bug is yours.
Classic arcade games are also small by necessity. They were built for hardware with a few kilobytes of memory, so they have one screen, a handful of objects and one core rule. That fits beginner scope almost perfectly, and it is why we keep coming back to them after a first game that stays tiny.
Picking the Right Game to Remake
Not every classic is a good second project. Here is how a few common choices compare for someone working in Scratch or a simple engine:
| Game | Core skill it teaches | Rough time for a first remake |
|---|---|---|
| Pong | Movement, collision, scoring | 2 to 4 hours |
| Breakout | Bouncing angles, lists of bricks | 4 to 8 hours |
| Snake | Grid movement, growing lists | 4 to 6 hours |
| Space Invaders | Enemy formations, shooting, waves | 8 to 15 hours |
| Asteroids | Rotation, momentum, screen wrap | 8 to 15 hours |
| Pac-Man | Maze logic, enemy AI | 20 hours or more |
Pick something one step above what you have already made. If your first game had a sprite that moved and collected things, Breakout or Snake is the right jump. Save Pac-Man for later. The ghost behavior alone has humbled more than one of us.
Study the Original Before You Build
Play the original for at least 30 minutes with a notebook open. Write down rules, not impressions. For Breakout, that list looks something like this:
- The paddle only moves left and right.
- Where the ball hits the paddle changes its angle.
- The ball speeds up after a certain number of hits.
- Bricks in higher rows are worth more points.
- The player has three lives.
That list becomes your task list. Each line is one feature, and you can tick them off in order. When we skipped this step on our Asteroids remake, we spent a whole session arguing about whether the ship should slow down on its own. Ten minutes of play would have settled it.
Scope It in Three Passes
We build every remake in three passes, and we do not start the next until the current one is playable.
Pass one, the bare rules
Colored rectangles, no sound, no menu. Just the core loop working. For Breakout that means a paddle, a ball, bricks that disappear and a way to lose.
Pass two, the feel
Now tune speed, angles and timing until it plays like the original. This is where you learn the most, because tiny numbers make huge differences. Changing ball speed from 6 to 7 can turn a calm game into a stressful one.
Pass three, the wrapper
Add score, lives, a title screen and sound. If you have not built a scoring system before, our guide on adding a score and high score covers the pieces you need.
Do Not Make a Perfect Copy
A lot of tutorials push for pixel perfect clones, matching the original's exact speeds, colors and sounds. I think chasing perfection is a trap for a learning project. You can lose a week trying to match a frame timing from 1978 that nobody playing your version will ever notice.
Aim for close enough that the game feels right, then stop copying. Pixel perfect accuracy is a skill for preservation work, not for learning to make games. The goal is to understand why the design works, and you get that by getting near it, not by matching it to the decimal.
Add One Twist and Make It Yours
Once the remake plays well, change exactly one thing. One change keeps the project finishable and teaches you how a single rule shifts the whole game. Some twists we have tried:
- Breakout where the bricks slowly move down, so waiting is punished.
- Snake where eating makes you shorter and faster.
- Pong where both paddles are controlled by one player.
The twist also matters if you share the game publicly. Use your own art, your own sounds and your own name for it. Game rules are generally not owned, but the original names, characters and artwork are, so a remake should look like your project, not a copy of someone else's.
Write Down What Broke
Keep a running note during the build with one line per problem and one line for how you solved it. Our Breakout note ended up with 14 entries, things like "ball tunnels through bricks at high speed, fixed by checking collision twice per frame" and "paddle angle feels random, fixed by splitting the paddle into five zones." That note is worth more than the finished game.
Why it matters: the next remake will hit half of the same problems. When Snake started skipping inputs, the fix was already sitting in the Breakout note. After three remakes you have a personal cookbook of solutions that no tutorial gave you, written in your own words for the tools you actually use.
Frequently Asked Questions
Is remaking a game cheating as a beginner?
No. Musicians learn covers before writing songs, and developers have always learned by rebuilding classics. You are practicing execution, which is most of the work.
Can I build these remakes in Scratch?
Yes. Pong, Breakout and Snake all work well in Scratch. Space Invaders and Asteroids are possible but need clones and careful use of variables.
How many remakes should I do before an original game?
Two or three is usually enough. After that, you will start wanting to change more than one rule, which is a sign you are ready to design your own.
The Practical Takeaway
Choose a classic one step above your last game, play it for half an hour with a notebook, and build it in three passes. Stop at close enough, add one twist, and give it your own look. You will finish faster than any original idea, and you will carry the skills straight into your next project. See more of what we are building in our projects section.
More in Projects
Projects
How We Built a Match Three Puzzle Game in Scratch
We shipped a match three puzzle in Scratch in nine days, and the first six of those days were spent building the wrong thing.
Projects
How We Built a Tower Defense Game in Scratch in Ten Days
The first playable version of our tower defense game ran at about nine frames a second once wave four started, and a tester...
Projects
How We Built a Two Player Pong Game in Scratch
Pong looks like the easiest game ever made: two paddles, one ball, a score.