A Napkin, a Vote, and a New Game Mode in 5 Days

The Napkin That put it together (avoid start per avoidList) It

We shipped a new game mode in 5 days because a student drew it on a napkin. The napkin sat on the studio table for a week before anyone took it seriously. It had a messy sketch, a few arrows, and the words everyone vs one super tank. That's it. Rewrite (trim anaphoric no X lists to two items max, drop the third). Just a rough idea from a player who wanted something different.

That player, a computer science student at the local university, posted the sketch on our idea board after we said we'd listen to anyone. They scanned the napkin and added a short explanation. The post got 40 upvotes in the first day, which was more than most balance changes we'd proposed. We saw it and knew we had to try. The idea was simple: ten players fight one giant tank with immense health and firepower. The tank is controlled by a player or an AI, we hadn't decided yet.

Here's what surprised us. The player who drew it wasn't a game designer and never claimed to be. They just wanted to see the mode work. That's the core of how to find indie game developers who care: you don't need a degree, you need an idea and the willingness to hand it over. We turned that napkin into a prototype in 48 hours, then spent the next three days turning the prototype into something we could play without breaking every few minutes.

The tank mode shipped under the name GIANT and it's live right now. You play it in the same browser client as everything else, no download, no install. It ran through 5 days because we had a deadline, everyone voted, and we didn't let perfection get in the way. We cut features we loved, broke a few things, and fixed them again before we went to bed on day five.

We learned that a napkin is a real design document if you treat it with respect. The sketch showed what mattered: scale, chaos, and one clear threat. We built around that and ignored everything else. That's the lesson of this whole thing. Indie games aren't about polish from day one, they're about shipping something that makes people want to come back.

Why Player Ideas Beat Our Roadmap

We planned to spend the next two months fixing matchmaking and adding a new map for DOMINION. The napkin changed that. We could have ignored the post and argued that our internal plan had better metrics behind it. But we promised something simple: everyone gets one vote, and the top ideas become the roadmap. The napkin won, and we had to follow through.

That's how indie game development works when you're a small team. You don't have a marketing department or a focus group, you have your players. Player votes are the closest thing we have to a crystal ball. They tell us what people want, not what we assume they want. When a sketch gets more votes than a new sniper rifle, that's a signal we can't miss.

Here's what that means for us as a studio. We're small, student-run, and mostly broke. We can't afford to build things nobody plays. That's why we lean hard on the idea board. It acts like a free playtest, from people who've never seen our codebase or our budget. That's why our community posts often lead our dev cycle, because they cost nothing but time and they tell us exactly what to build next.

But we also know that not every idea is a winner. Some posts get votes because they're funny or because someone's friends spam the button. That's fine. We can filter that out by Building fast and seeing what sticks. The napkin mode got built because we could test it in a week. If it fails, we lose a week. If it works, we have a new mode that players feel ownership of.

For anyone wondering how profitable is indie game development, this is the real answer. It's not about copying the latest trend or chasing a publisher's checklist. It's about finding a small group of people who care enough to draw you a napkin and tell you what they want. That passion turns into regular players, and regular players become the reason you can keep the server on.

How We Built the Whole Thing in 5 Days

Monday we saw the vote count and told everyone we'd ship by Friday. That was a risky promise, but it worked because we killed our ego and cut scope hard. The first prototype was one giant health bar, one player-controlled tank, and nine small fighters with basic weapons. Rewrite (trim anaphoric no X lists to two items max, drop the third). Just a tank that shoots, and a group of players who have to survive.

We used the same browser engine as the rest of the game, so we didn't have to rewrite anything from scratch. That saved us a lot of time. We added a new game mode flag, a simple lobby that reads the mode name, and a rough map that's basically a flat field with some crates. The crates are just boxes, but they give the fighters somewhere to hide. That was enough for the first playable version.

Tuesday we hosted an internal test with the whole team and a few friends. The tank was too weak, so we tripled its health. It was still too weak, so we gave it a shield that regenerates. That made the fight last longer, but the tank felt unfair, because it could one-shot everyone. We rebalanced the damage numbers and made the tank's shots slightly slower, with a clear telegraphed glow so you can dodge.

Wednesday we fixed a bunch of little bugs. The crosshair didn't line up on the server, hit detection was off for bigger characters, and the tank's machine gun fired in a weird pattern. We also made the tank's weak point visible: a glowing red core on its back. That gave the fighters a clear goal, rather than just spraying bullets and hoping for the best. The core has a percentage of damage taken, and when it hits zero the tank explodes.

Thursday we ran a public beta on the Discord server for about six hours. Around 300 players tested it. We watched every match and wrote down what worked and what didn't. The main fix was the spawn timer: fighters were getting killed right after spawning because they appeared in the open. We moved the spawn points into sheltered corners with a short invulnerability period, and that solved most of the frustration.

Friday we polished the interface and pushed a final build. We added a text prompt to tell new players about the weak point, and we changed the tank's color to make it more distinct from the background. The launch at 6 PM was clumsy, with a few crashes, but it stabilized within the hour. We watched the first few matches from the studio, and then we went home and slept.

What You Get to Play Right Now

The GIANT mode is free to play right now. Rewrite (trim anaphoric no X lists to two items max, drop the third). You load the game, pick a mode, and you're in. The tank fight plays out in a small, wrecked city map that we cobbled together from existing assets. It's not pretty, but it's functional, and it fits the chaos.

You can either be the GIANT or one of the fighters. If you're the GIANT, you move slowly, take a lot of damage, and dish out massive attacks. Your job is to block the fighters from reaching your core and to survive a ten-minute timer. If you're a fighter, you respawn after a few seconds, but each time you die, the tank gets a little stronger.

We added a score system that rewards teamwork. You get points for dealing damage, but you get a multiplier if you're near another fighter. That encourages you to hold positions together, rather than running away solo. The winning side gets a small in-game currency reward, which you can spend on cosmetic items in the Loadout Lab.

What you won't see yet are extra maps or a matchmaking system that separates new players from veterans. We deliberately held those back because we wanted to ship the core idea quickly. That's a trade-off we're comfortable with. It's better to have a rough, playable mode than a polished one that never ships. We'll add more maps and balancing later, based on how you play.

So when you ask is indie game development worth it, the answer is yes when it feels like this. We built something in a week that you can play right now, and we did it because a player cared enough to draw it. That's the kind of energy that keeps a small studio going, and it's the reason we keep the idea board alive.

What This Teaches Us About Finding Devs

Our studio is three people plus a handful of volunteers. We're not a big company with a hiring pipeline. We find developers by making it easy for players to step in and contribute. That napkin was a better pitch than any resume we've seen. It showed creativity, bravery, and a willingness to fail in public. That's exactly the kind of person we want to work with.

If you're a player and you want to get involved, the best move is to post an idea on the board. That's the same as sending us an application. We read every post, and we keep an eye on people who explain their thinking, not just their wish. A single well-reasoned idea is worth more than a portfolio of unused concepts.

For a small studio, how to find indie game developers isn't about cold emails or job boards. It's about Building a community where ideas are welcome and action is rewarded. When you treat players like co-designers, you get a pool of people who already understand your game. They don't need onboarding, they need a chance to make something real.

A lot of people ask how profitable is indie game development and whether it's a good career. If you're doing it for the money, you're doing it for the wrong reason. This week we shipped a mode that cost us sleep and stress, and the reward was watching people play it. That's the payoff. It's not guaranteed cash, but it's a real feeling that a big corporation can't buy.

So if you're a student with a sketch or a player with a half-formed idea, know that we're listening. You don't need to be a professional artist or coder. You need to care enough to write it down and vote for it. That's how our studio works, and that's how we'll keep finding people who want to build with us.

What's Next on the Idea Board

We're not stopping with GIANT. The idea board is full of other wild ideas, and we're already looking at the new top votes. Right now there's a post about a grappling hook, another about a weather system that changes mid-match, and a third about a coop horde mode where players share a single health pool. Each one has a small but passionate group behind it, and they're climbing the charts.

We're going to keep the same formula we used for this napkin: pick the top vote, build a rough version fast, and put it in the game within a week or two. That means we'll ship more broken, rough, exciting features than a polished game would offer. We think that's a fair trade, because you get to play these ideas while they're still hot, not after a year of meetings.

Our next step is to improve the idea board itself. Right now it's just a vote counter, but we're planning to add a preview section where you can see concept art or screenshots from a sketched idea. We might also add a dev log that shows how long each idea took to build, so you can see the cost behind each vote.

We're also thinking about a system that rewards players who vote for ideas that ship. If you voted for a mode that becomes permanent, you could get a unique badge or a small cosmetic item. That's a way to say thanks, and it encourages people to vote for things they truly want, not just jokes.

For us, this is how indie game development should feel. It's chaotic, collaborative, and never boring. We want to keep finding developers in our community, and we're proving that a napkin can turn into a feature in five days. Next time you vote, you might be the one who draws the thing we ship.