LD58 was my first foray out of the tutorial zone. Fortunately for me, I got to make Mailbox Mania together with a much more experienced game dev in Wuppos.

In a coffee and brainstorm session on the first morning, we made a long list of all the things, concepts, and gameplay elements we could think of around the theme "Collector". We narrowed it down to two ideas that we were most excited about: an isometric racer with collectibles and a deck-building trading card game. Next, we spent a strict fifteen minutes scoping out the 72-hour version of each idea. It quickly became clear that we had a much more coherent vision for the racer than for the card game.

Both of us really liked the image of a frenetic mail van hurriedly picking up mail all over a quiet town and we knew that we wanted to make an arcade-style game with a fixed camera and a running timer. The rest just fell into place: - The van must be fast and the controls should be challenging but satisfying. - The map must have sharp turns and precise drifting should be rewarded. - Power-ups should present meaningful choices: Is it better to go for extra time (or speed) or another mailbox collection?

Wuppos picked up all of the art for this project. On day one, he got started on the sprite stacking tech, while I set up a test map to work on the van controls. It turns out that the key to making satisfying driving controls is to consider the movement of the front and rear wheels individually (e.g., only the front wheels turn), and to counteract player-controlled acceleration with friction and air drag. I found it quite challenging to make the controls feel good. There are a lot of variable parameters and because keyboard input is binary, there is no notion of how strongly the player turns the wheel. Our goal was to have something playable at the end of day one. So, although I was not happy with the van controls, I moved on to coding the game manager, the pick-ups, and the collisions, while Wuppos was finishing up the first sprites for all the major game elements.

On day two, it was clear that getting the driving to feel good was a priority. As I watched Wuppos have a crack at it, I learned my first big lesson of the game jam: juice doesn't have to obey the laws of physics :scream:. We could simply make the van drift when it would feel good for it to drift. He also found a sneaky solution to the binary car steering problem: tying the turning angle to how long the key is pressed. Over the rest of the day, I worked on the power-ups, start and end screen, game timer, and scoring. By the end of the day, we had a complete, legitimately fun game on our hands!

I had to sign off at the end of day two due to unfortunately timed work constraints on Monday. But, I had the distinct pleasure of checking in that evening to find the truly insane levels of polish that Wuppos single-handedly added to the game! There were now tire tracks, smoke and flame particles, additional art assets on top of a slapping soundtrack and a beautiful title screen. I realised that I had not been correctly gauging how important the little things are in taking a game to the next level: big lesson number two from this jam.

Anyway, big thanks to Wuppos for letting me jam with him! I had a great time and I'm revved up for the next one. Please do check out Mailbox Mania if you haven't yet. We've already gotten some wonderful and super helpful feedback and we would love to hear from you too!

I’m really proud of this one! The fundamental idea behind Robo Phone Home is that signals take time to get from point A to point B. With this as our guiding light, @Wuppos and I started the dev process with a morning brainstorming session coming up with a game mechanic and theme.

Our early ideas focussed on spaceship—mission-control dynamics on a long interstellar mission, with signals between the two transmitting at the speed of light. But we decided that we wanted to keep both parties on one map where the on-screen visual distance between them corresponded directly to the signal travel time. This didn’t quite feel right for interstellar distances, so we scaled the theme down to a robot and a control tower.

We immediately ran into a challenge: a time delay between input and response is inherently unfun. Our game must have a control scheme that feels like more than just controlling a robot character with lots of input lag. We realised we could get the perfect blend of responsive controls and meaningful signal travel times by centering the game around aiming instructions at the robot. The rest of the game sort of just designed itself.

We spent most of the first day implementing the robot/tower/signal mechanic, and making sprites for the robot, tower, and walls. We tried the mechanic on a test map with just walls to get a feel for what we were making. We discovered that we were making a puzzle game with an aiming mechanic. Perhaps we could call it a dexterity puzzler or a puzzle shooter (please let us know if you have a good idea for the genre name!). We had a second brainstorming session coming up with lots of different types of obstacles and interactable map elements, a small fraction of which we implemented and added to the six levels in our jam entry.

This was my first time making a puzzle game. Now that we’ve gotten some feedback, I’ve learned that it’s far too easy to make puzzle games a tad too hard. Testing your mechanic throughout the dev process through all its iterations actually makes you somewhat good at it and you lose sight of what it’s like for someone who’s just picking it up for the first time.

I want to say a quick thank you to all the folks who played Robo Phone Home, and left us kind words and useful feedback! Another quick thanks to @Wuppos for jamming with me again and lending his unique soulful pixel art style to the game (I have it easy)!

Hello friends,

We have a very exciting announcement to make: We are developing Robo Phone Home into a full game! Woooooo :)

We fell in love with the game as we were making it. After seeing the thoughtful feedback and amazing scores we got from the Ludum Dare community, we felt even more motivated and decided to go for it!

Look out for a demo drop in fall 2026.

Join our (NO SPAM) mailing list to stay up to date with our release schedule, get alpha access and other freebies, and become precious early supporters of our little project.

--Wuppos and Pastry Chef