County Stood is built the way a competitive shooter has to be built: the rules run in one place, at a fixed rate, with no rendering code allowed anywhere near them.
Input becomes a serialisable command object, the command feeds a fixed 60Hz step, and only then does anything get drawn. The simulation never imports the renderer, which is what keeps a hit registering identically no matter what your frame rate is doing.
Recoil is an authored list of offsets in degrees, not a random kick. The rifle walks up, pulls left, then settles into a repeating figure. Hold it long enough and you will know where the thirtieth round goes.
Kills pay a bounty, the buy window opens near your own spawn, and ammunition is a purchase rather than a refill. Respawning does not top you up, which is what gives dying a price.
Bots feed the same command objects a human does, through the same tick function. That is deliberate: the day an authoritative server exists, it runs the simulation that already shipped rather than a second copy of it.
One point per shot, in firing order. Vertical and horizontal offset in degrees, before per-tick decay. Origin is your crosshair.
Standing, crouching and going prone change your speed, your silhouette and your spread at the same time. Dropping prone cuts your cone of fire in half and cuts your speed to a fifth. The trade is the decision.
Crouch is bound to C rather than Ctrl. Ctrl and W together close the tab in Chrome, and a web page cannot stop it.
The 60fps promise is measured on a mid-range laptop with Intel integrated graphics at 1080p, not on a development machine.
Target hardware · Intel iGPU laptop @ 1080p
