"Honest idle" has been on my design pillar for a long time, but I only understood what that phrase actually demands of me when I had to decide on a number nobody was ever going to see, and that still defines the entire game under the hood: how many defeats per hour one of your esvas can land against a quadrant, at the cap, once it's already one-shotting everything.
The number I settled on is 450 defeats per hour. It's not decorative — it's the official central value for every calculation in the game. Every rarity math, every estimated time-to-something-rare, every comparison between "focusing" and "exploring" species, this whole structure is built on top of 450/h as the reference point. If I change that number later, I have to publicly redo every calculation that depended on it — which is exactly why I've resisted changing it without a real need.
What "honest idle" means in practice, no rhetoric
Farming never requires walking. The server simulates the quadrant where you stopped, even with the game closed — that's how "absence never punishes" becomes a mechanic instead of an intention. Walking is a choice, not an obligation: the map turns into fast-travel between quadrants you've already opened, with a small Credit fee just so it isn't free for nothing. Below the 450/h cap, the defeat rate emerges from actual combat — your esva's strength times class effectiveness times your four active moves. It's not a fixed number hidden behind a progress bar; it's the calculable result of the decisions you made putting together your bolsa.
And the principle that sums it all up: what you see is what you get. The cadence the game renders on screen — your esva landing hits, the enemy going down — is the real reward rate, and the server replicates that exact same rate while you're offline. There's no slower "true" version running hidden behind a faster visual version just to look good. If I broke that rule even once, the rest of what I have to say about odds transparency (which is a whole other post) turns into marketing copy.
Presence has two levels, and the second one almost didn't exist
Passive presence is just having the tab open — it gives you a streak bonus all on its own, with zero effort from the player. The second level, manual mode, I almost cut from the beta scope because it seemed like too much work for a system that, by definition, exists to reward people who AREN'T actively playing. I decided to keep it because the counter-argument was stronger: if active presence gives you nothing more than passive presence, why would anyone actually play? In manual mode, you use WASD or arrow keys to move, fire your four active moves each on its own cooldown, and pick a buff — more damage, more loot, more XP, or a 1.08x chance of containment. That buff stacks with the VIP bonus, but always stays below it. It's real action gameplay, for whoever wants it, required of no one.
The anti-wall rule, and the number that enforces it
Every boss in the game needs at least two active ways out besides simply hitting harder: persistent damage that carries over between attempts (you don't lose progress if you fail), weakening quests that lower the boss's defense, and aggressive counter-picking that gives a 50% effectiveness bonus to whoever levels up the right class against it. The rule comes with an enforcement number attached: if telemetry shows the median (p50) time a player spends stuck on the same boss goes over 6-8h, that trips an alert — it's not a designer's opinion, it's a measurable limit that triggers a review.
The detail that answers the obvious question: "what if my esva faints while I'm not looking?"
There's no individual fainting in ESVA, and that sentence is also an absolute rule, not a figure of speech. If one of your esvas goes down in combat, it goes back into the frasco — with the same containment visual effect played in reverse — and the next one in the bolsa automatically steps in. Idle doesn't stop because one esva went down; it only stops when the whole bolsa goes down at once. In practice, that means I don't have to design any individual fainting animation, because it's never the final state of anything — it's always an instant transition to the next esva. Manual leader-switching has a small cooldown, around ten seconds, just to keep someone from swapping esvas on every single hit to exploit an effectiveness edge — but that's active-combat friction, not an absence penalty.
What I still haven't calibrated
The 450/h cap and the 6-8h telemetry threshold are numbers I settled at my desk, with a calculator, without a single real player testing them. That's the kind of decision that only proves itself right or wrong with beta data — and I know, writing this now, that there's a real chance the number will have to change after real people spend eight hours straight fighting the same boss and send me a screenshot. I've marked this as pending calibration, not final, because faking certainty here would be exactly the kind of lie "honest idle" exists to prevent.