What Actually Happened
A player posted a clip. The clip was 7 seconds long. It showed their character dying, then the camera sitting on the body while a 3-second countdown ticked down. The caption was one line: this is longer than the old death. They were right. Before the timer, death was instant and you were back at spawn in under half a second. After the timer, you watched a corpse for three full seconds. That is a downgrade dressed up as a feature.
The timer came from a board idea with 12 votes. The pitch was that instant respawn felt disorienting, like you teleported. Fair note. We shipped a 3-second timer as a test. We did not measure what it did to the actual wait. If we had, we would have seen the problem before the clip did. The player saw it in one match. We should have seen it in the build.
We pulled the timer 40 minutes after the clip landed. Not 40 minutes after a meeting. 40 minutes after the clip. The revert is timestamped in the build log. Average wait per death went from 3.1 seconds with the timer to 0.4 seconds after the revert. That 0.4 is the old number, the one we should have protected. The 12-vote idea is back on the board as Planned, because the disorientation note was real. The fix was wrong, not the complaint.
This is the kind of thing that happens when a student team ships fast between lectures. You ship a fix, you feel good, then someone with a phone and a clip shows you the fix made the game worse. That is the job. We would rather get caught in 40 minutes than in a post-mortem six months later. So this is the ledger entry. What we got wrong, who caught it, what the numbers say now.
If you are one of the people who plays browser games to play in school, you know the pain of a wait. You have a window between classes. Three seconds of watching a corpse eats that window. The old death was fast. The new death was slow. You told us. We reverted. Your first three seconds after death are yours again, and the clock starts on your terms.
The Numbers Before and After the Revert
We track wait per death as the time from death to your character being controllable again. Before the timer, that number averaged 0.4 seconds across a session. Nothing fancy, just fast. With the 3-second timer, it averaged 3.1 seconds. That is roughly 7.7 times longer. You feel that. You feel it more when you die 10 times in a RUSH wave and the timer stacks up to 30 seconds of your life spent watching a body.
The clip made the case better than our own dashboard did. The player did not send a paragraph. They sent the 7 seconds. That is easier to act on than a survey. We watched it once and knew. The revert was a one-line change and a build. The 40 minutes includes the build and the push. Not a sprint. A single decision made quickly because the evidence was right there.
After the revert, the average went back to 0.4 seconds. We ran the same wave map for 90 minutes with a small group to confirm. The wait number held. Nobody asked for the timer back. That was the test. If people wanted the cinematic feel, they would have said so. They did not. The disorientation complaint from the 12 voters is still open. We are testing a short camera snap instead of a timer, but it is not done yet. When it ships, you will see the wait number before we call it fixed.
This matters for the broader question of what is the best browser game to play. The best one is the one that respects your time. A 30-second load does not help if every death costs you 3. A free online game no download for kids or for anyone else lives on the small waits. We treated the death wait as a small thing. It was not small. It was the thing between you and the next fight. The ledger now has the number in it for the next time we are tempted to add a timer.
Why the Vote Still Counts
The 12 people who voted for the timer were not wrong to want it. Death felt like a teleport. That is a real feeling. We shipped the wrong fix, but the underlying note was right. So the idea is back on the board as Planned. It does not disappear because our first attempt failed. This is the part of the idea board that people do not expect: a vote does not die with a bad build. It goes back to Planned and we try again with the wait number as the guardrail.
One player, one vote per idea. That is the rule. The top-voted ideas move Planned to Building to Shipped, and you can watch the status change. This time you watched it go Shipped and then back to Planned in the same day. That is not a bug in the system. That is the system working. A vote is a signal about what you want, not a promise that our first attempt is good. We owe you a real attempt, and we owe you the data when the attempt fails.
The clip came from a player, not a tester. That is the part we keep learning. Our testers played the build and did not flag the timer. A player with a phone flagged it in one match. The lesson is not that testers are bad. The lesson is that players see the thing you stopped seeing. If you want a say in what gets built, the clip is as loud as the vote. Post it. We read them. This one moved a build in 40 minutes.
For anyone building a brand community building playbook for saas, the takeaway is simple. The community is not a marketing channel. It is the QA team you did not hire. They will catch the fix that made things worse, and your job is to thank them and revert fast. We are a student team in Tunisia running this between lectures. We do not have a big QA budget. We have you. That is the platform: a board, a clip, a revert, a timestamp. No account needed to post. No card. Just the link.
What You Get Now, and What Is Still Open
You get the fast return. Death puts you back at spawn in about 0.4 seconds, and the spawn rule still checks enemy line of sight before it places you, so you are not landing in someone's crosshair. That spawn rule is the reason the fast return is safe. If we had kept the 3-second timer, you would wait longer and still land in a bad spot sometimes. The old behavior was faster and no worse on spawn safety. That is why the revert was easy. The timer was not buying you anything.
The 12-vote idea is not finished. The disorientation note is real, and we are testing a short camera snap to soften the teleport feel without adding wait. It is not done yet. When it ships, we will post the before and after wait numbers and the clip that shows it. If the snap adds even 0.2 seconds to the average wait, we will not ship it. That is the guardrail the clip taught us to set.
We also added the death wait to the ledger page. It sits next to spawn deaths and load time. You can see the number move when we change something. That page is the reason this entry exists. If we are going to publish the build process while it happens, we have to publish the parts where we get it wrong. A ledger with only wins is a trailer. You can load the game in your browser and see the current wait for yourself. No install. No card. GC 300 and SC 15,000 to start, both earned by playing, never bought.
If you are looking for free online games no download for girls or for anyone in a school lab, the same rule applies. Your time is the thing. We will keep publishing the wait number and the reverts. If you catch the next fix making things worse, post the clip. We will read it in the same window between lectures. The vote is yours. The revert is ours to earn. That is the deal, and this ledger entry is us holding up our end.