How voting and feature requests work
A holo isn't finished when it first loads. Anyone who plays it can suggest what it should add next, and when enough people back the same suggestion, the console builds it into a new version on its own.
Two kinds of votes
There are two buttons that count as votes on HOLO X1, and they do different jobs.
The upvote next to a holo's title says you like the game. Upvotes decide where a holo sits on the Top shelf on the home page, and they count toward its engine tier. Tap it again and your vote comes back off.
The votes on feature requests decide what the game turns into. Each holo has a list headed "What should it add next?" under the game. Every request in that list has its own vote count.
Suggesting a feature
Type the change you want in the box under the game and press Suggest. A request can be up to 160 characters, so keep it to one change: "a boss every 10 points" works better than a paragraph that asks for five things.
Your suggestion counts as its first vote. You can make up to 6 suggestions a day across all holos.
Good requests name something a player would notice in the first minute of play:
- A new enemy, hazard or power-up.
- A rule change, like a timer, lives, or a combo bonus.
- A second stage or a speed-up after a set score.
- A fix for something that feels wrong, like a jump that's too floaty.
When a request gets built
Once a request reaches 3 votes, the console starts building it. The AI takes the latest version of the game, adds the change, and runs the result through the same automatic check every holo passes before anyone can play it.
A holo builds one feature at a time. While a build is running, other requests keep collecting votes. A request that passes 3 votes during someone else's build goes in on its next vote after that build finishes.
If the build works, the holo gets a new version number and the request is marked as built, with the version it landed in. If the console can't get a working version, the request is marked failed and the game stays as it was. Nothing breaks the version people are already playing.
Older versions stay playable
Every version of a holo is kept. Once a game has more than one, a version menu appears beside it, and you can go back and play the first build or any version in between. Each version is labelled with the request that made it, so the menu doubles as the game's changelog.
Each holo also has its own page at holox1.com/play/ followed by the holo's id. That page lists the full version history, so you can see how a game grew from one sentence to its current form.
Votes and engine upgrades
Upvotes and built features also move a holo up the engine tiers. A holo moves from Standard to Turbo at 10 upvotes or 3 built features, and from Turbo to Hyper at 40 upvotes or 8 built features. Reaching a new tier triggers one automatic remaster of the game on the stronger engine. The engine tiers guide explains what changes.
Who can vote
You don't need an account. HOLO X1 gives your browser a random id the first time you visit, and your votes are tied to it. Clear your browser data or switch devices and the console treats you as a new player.
The console also has a daily budget for builds. On a busy day it can run out, and a request that reaches 3 votes stays open until the budget resets and someone votes for it again.