Content record
Archive
No season has finished
Nothing here entered the game by vote. Season 1 has not run, so there is no winner, no count and no proposer to credit. Everything currently in the game was written by the developer, and this page says so rather than leaving the column blank.
Seasons
| Season | Candidates | State | Winner |
|---|---|---|---|
| 1 — Health and Safety Review | Static Cling, Overtime Pay, Budget Cuts | Gated and shipping in 0.3.0. No round has opened; see the vote page | None |
The shipped catalog
Thirteen perks, permanent, offered three at a time when you level up. Ten of them rewrite projectile behaviour and compose with each other rather than replacing each other, which is where a run stops being predictable. All are developer-authored.
| Perk | What it does | Proposed by |
|---|---|---|
| Afterburn | Hits ignite targets. The follow-up paperwork is also on fire. | Developer |
| Emergency Padding | +25 maximum health and refill it. OSHA would probably approve. | Developer |
| Greased Laces | Move 1.5 units faster. Braking remains your problem. | Developer |
| Hungry Homing | Pellets steer toward nearby enemies. They have developed opinions. | Developer |
| Impatient Trigger | Fire interval ×0.8. Patience was never part of the build. | Developer |
| Municipal Giant | Pellets become enormous and hit harder. Zoning approval pending. | Developer |
| Paperwork Piercing | Pellets pass through two extra enemies. No signatures required. | Developer |
| Pocket Cluster | Expired pellets scatter five children. Tidiness was never promised. | Developer |
| Return to Sender | Pellets turn back after 0.65 seconds and can hit you. Delivery remains your problem. | Developer |
| Ricochet Rounds | Pellets bounce twice. Walls have joined the aiming team. | Developer |
| Splitting Shot | Impacts produce two smaller pellets. Basic arithmetic, weaponized. | Developer |
| Velocity Problem | Pellets accelerate in flight. The speed limit has left the building. | Developer |
| Volatile Payload | Impact and expiry create blasts that can hurt you too. Warranty voided. | Developer |
Candidates on file
| Candidate | Season | Gate result | Status |
|---|---|---|---|
| Static Cling | 1 | Accepted on the first run | Awaiting a round |
| Overtime Pay | 1 | Accepted; returning pellets can hit their owner | Awaiting a round |
| Budget Cuts | 1 | Rejected as written, eased to one extra split, then accepted | Awaiting a round |
The rejection is kept on the record rather than tidied away. As first written, Budget Cuts requested 1,486 projectiles with 808 refused and 255 of 256 pool slots filled — bounded only because the safety layer was holding it back. Eased, it measures 506 requested, about 6% refused and 117 slots. The numbers behind each verdict are on the vote page.
How proposals will be credited
When a proposed perk ships, the person who proposed it is named here, next to the season it won and the values it shipped with. The end-of-run Incident Report already prints an award every time you die and has room to print who proposed the perk that killed you.
Nothing is credited yet because nothing has been proposed from outside. The pipeline that will carry those proposals — model-generated data, a whitelist importer, a headless gate — is built and tested; what it has not had is a first outside idea to run through it.
Rejected proposals are kept too. A folder of files that quietly failed is a folder somebody eventually ships by mistake, so the gate deletes the resource and keeps the record.