The vote that moved a feature up two weeks
Last week, a new weapon hit 212 votes on our ideas board. That was enough to jump the queue and land two weeks earlier than planned. We shipped it in a matter of days. You saw the announcement, you played it in the same week. What you didn't see was the map we had to push back to make that happen. That map was originally scheduled for this week. Now it's coming two weeks later. We made that call with your votes as the reason. We think that's the right way to run a game.
This is not a hypothetical. It's the actual process we use every single day. When a feature gets enough votes, it moves to the top of our list. The version we were working on, the map, it had to wait. We had a choice: stick to the old plan and tell you we'd get to your idea later, or reshuffle and give you what you actually asked for. We chose you. That's not a marketing line, it's just how the system works.
Here's why it's here: because you voted. Not because we had a slot to fill or a patch to pad. The community asked for a fast, aggressive option, and you got it. The SMG rewards close-range play, with a high fire rate and a wild recoil pattern. It changes how you approach tight corners and objective points. If you've played it, you know what it does. If you haven't, go try it.
We know that every vote has a cost. When you ask for something new, something else has to give. That's true in any project, but most studios hide it. They act like everything just happens. We're not doing that. We're showing you the schedule and the tradeoffs, real numbers and all. You get to see exactly what your vote buys and what it delays. That's the deal we made when we built this board.
This feature moved up because of a specific community effort. A small group of players rallied around it, shared it on Discord, and pushed it past the threshold. It wasn't the most votes we've ever seen, but it was enough. That's the kind of momentum that changes our timeline. And we love it. It means the board is alive, not just a suggestion box nobody reads.
Coming next: a new wave mode built for RUSH
Right now, the next item on our roadmap is a new wave mode for RUSH. It's designed to push you beyond wave 20 with new enemy types and environmental hazards. The original design was supposed to be smaller, just a handful of new spawns and a boss. But your votes on a related idea turned it into something bigger. We saw the pattern: you want more variety in endless mode, more reasons to coordinate with your squad. So we're expanding the scope.
That expansion is exactly what pushed the map out of the schedule. The wave mode is now a two-week version, not a one-week tweak. It needs new models, new AI routines, and a bunch of balance passes. We started on it right after we shipped the SMG. It's the kind of work that doesn't show up in a patch note until it's done, but it's happening.
You can vote on the specifics if you want. The idea board has a thread for wave modifiers, and the top suggestions are already shaping the design. One idea asks for a shield-type enemy that only takes damage from melee. Another wants a fog mechanic that shrinks the arena every two waves. Those are live ideas, and they could make it into the final version if they get enough votes. That's your call.
We're also using this wave mode to test a new cosmetic reward system. Nothing that affects balance, just a new set of weapon skins you can unlock by hitting milestone waves. We're not selling them, they're part of the game. You earn them by playing. That's been the core promise from day one, and this mode is another example.
So if you've been playing RUSH, expect a deeper challenge in the next few weeks. We're aiming for a release in two weeks, but real life happens. We'll keep you updated if the timeline shifts. And if we miss, you'll know why.
What your vote says about your priorities
Every vote on the ideas board is a signal about what players actually want. When you vote for a weapon, you're saying combat variety matters more than a new map. When you vote for a wave mode, you're saying PvE content is a priority. We read those signals and we act on them. That's not a gimmick, it's the core of how we decide what to build next.
But most communities never get to see the consequences of their choices. They vote in a survey, the company publishes a roadmap, and nobody knows what got cut. We're doing the opposite. We show you the real priority list, and we update it whenever the community shifts it. Last week, the SMG was number 14. This week, it's shipped. The map dropped from third to fifth. You get to watch it happen, every week.
That transparency is also a test of trust. What we actually do matters more than what we say we do. If we call ourselves community-driven and then ignore your votes, that gap shows fast. So we put our money where our mouth is. You vote, we build, and we tell you exactly what that costs.
There's no loyalty program here, no points, no tiers. It's simpler than that: your vote is the reward. You don't get a badge, you get a game that actually changes because you spoke up. That's the kind of loyalty you can't buy. And it's why we've kept the board so simple. One vote per player. No paid boosts, no way to game it.
The system isn't perfect. Sometimes a feature slips because of a bug, or because someone on the team gets sick. But when a delay happens because of a vote, we'll tell you. We'll name the feature and explain the tradeoff. You're not just playing this game, you're helping build it, and you deserve to know why.
The map we pushed back, and why it's still coming
The map that got delayed is called 'Terminal.' It's a small, dense arena set in a rusted train yard. We've been hyping it for a while, and we know a lot of you are waiting. The design is done, the geometry is final, and most of the textures are in place. What's left is the lighting pass and the spawn logic. Those are the kind of details that make a map feel fair and readable, so we don't want to rush them.
When the SMG jumped the queue, we had two choices. We could cut corners on the map and ship it half-baked, or we could delay it and give the team time to finish it properly. We chose the delay. That's a rare thing in game development, where scope is everything. But we think a delayed map is better than a broken one. You've told us before that you hate spawning in a bad spot, and we listen.
The new target for Terminal is two weeks from now. That's the same week as the wave mode, so it's going to be a big patch. That's a lot for a small team to ship at once. We've been pulling longer hours to make it happen. That's our choice. We'd rather ship quality than hit an arbitrary date.
Some of you might be disappointed, and that's fair. But here's the other side: when Terminal lands, it's going to be the best map we've ever made. We're using it to test a new verticality system, with ziplines and breakable floors. That's a direct result of another idea that got voted up last month. So even the delayed map is tied to the community's voice.
We also learned a lesson from this schedule scramble. We're going to add buffer time between major features, so a surprise vote doesn't push the next thing too far. But we're not going to stop prioritizing your votes. That's the line we won't cross.
What this means for future votes
Every Wednesday, we lock the weekly version and review the board. Whatever has the most votes gets pulled into the next sprint. That's the rule. It works because it's simple. You don't need a hundred-page rulebook, you just need a clear signal. And your vote is that signal.
But sometimes it's not that simple: sometimes the top idea is too big to ship in a week. It might need months of work, like a new mode or a full map. In that case, we split it into parts and ship the parts. The vote still counts, it just takes longer to fully arrive. We've done that with the DOMINION mode, which started as a small prototype and grew through a bunch of updates. Your patience is part of the process.
We're also kicking around an idea for players who give consistently good feedback: early access to prototypes. No pay, no perks you can sell, just a direct line to what we're building. We haven't launched it. It's on the board. If you've got thoughts, vote on it or pitch your own.
We're also thinking about how to protect the game itself. We're free, we run on donations and sponsors, and we want to keep it that way. That means keeping our assets safe from data mining and clones. We've already seen copycats rip our UI and sell it as their own. A legal team won't fix that, so we're leaning on the community to spot it instead.
You're the ones who keep us honest. You send us clips of bugs. You report cheaters. You call us out when we mess up. That's more valuable than any paid service. So if you see a suspicious version or a YouTube tutorial repacking our mode, tell us. We'll take it from there.
The takeaway: your vote is real influence
We've been doing this for a while now, and the pattern is clear. When the community gets involved, the game gets better. Not because we're geniuses, but because we're listening. The SMG is in the game because you asked for it. Terminal is delayed because we made a choice. The wave mode is bigger than planned because you wanted more depth. Every one of those changes is a direct result of your input.
If we ever hired a consultant to tell us what players want, they'd know less than our own ideas board does. Nobody outside this community knows the game like you do. So we don't bother. The board is our compass.
If you're new to the game, here's how it works: go to the ideas board, find something you like, and drop your vote. You get one per account. If you want to change the roadmap, that's your lever. It's simple, and it's honest. There's no backroom deal, no pay-to-win. Just your judgment and our action.
Same goes for events. The community cups we run come from your suggestions too. The last event format, 4v4 elimination, came from a comment on the board. We didn't invent it. We just built it. That's the whole point.
So thanks for moving that weapon up. We shipped it because you wanted it. The map will come, the wave mode will come, and every other idea you vote for will come. Some faster, some slower. But they all come because you made them real. That's the tradeoff of a community-run roadmap, and we wouldn't have it any other way.