https://oskiewar.com/jev-vs-jev runs the real Oskiewar simulation with two independent Jev controllers. Each chooses a direction and action from its own visible-world snapshot. The built-in bot never supplies input on this route. Jev chooses long walks (180 ms), short steps (55 ms), face taps (20 ms), or standing still independently of its attack. Action buttons hold for 150 ms (450 ms for a full jump); movement releases at its own deadline so a punch does not force a fighter to run past its target. Observations include airborne state and available attack limbs; unusable attacks are excluded from Jev's choices. Jev can also choose a double-down drop, a fixed two-press sequence within the game's combo window, to descend through platforms. No response means neutral input; stale responses and old-round responses are discarded. Transient provider failures leave a fighter neutral while it requests a fresh decision; three consecutive failures stop the match.

Combat now uses rectangular hurtboxes, active attack boxes and guard boxes. Tab shows those same collision boxes. Punches have 5 startup / 3 active / 9 recovery frames; kicks have 8 / 4 / 14. Recovery cannot be canceled by another strike. Crouch-punch, low-kick, crouch-block and timed jump-attack sequences are available. Each observation includes box-based strike reach probes, posture and remaining recovery. The probes hold positions fixed; the 200 ms velocity estimate is only an estimate, not a simulated future. A bounding-volume tree narrows collision and nearby-platform queries. Full combo planning and hitstop remain future work.

The page shows separate provider-reported cost, input/output tokens, decision counts, and browser round-trip latency. Simulation stays at its normal rate while decisions arrive asynchronously. It is not frame-by-frame inference. Stop and hidden-tab handling release both pads. A match lasts 60 seconds. The demo does not publish replays or send match telemetry to PostHog.

POST /api/oskiewar-jev holds the OpenRouter key on Lith. A random match ticket expires after 75 seconds and permits at most 150 calls per seat. MongoDB atomically reserves 300 calls per match against a global 20,000-call UTC daily limit. Reservations are not refunded. Starts are limited to one per minute per source address in the serving process, and that process allows at most 12 concurrent decisions. Database failures refuse paid calls. TTL indexes remove expired ticket/counter records. The daily call ceiling is a request limit, not a fixed dollar ceiling; provider pricing can change.

node --env-file="$HOME/.config/aesthetic-computer/jev.env" xbox/tools/jev-vs-jev-dev.mjs
# http://127.0.0.1:8791/jev-vs-jev

The loopback development server uses expiring in-memory match counters. Production uses persistent Mongo counters. The shared model input normalizer accepts only bounded game coordinates, booleans and fixed movement-option kinds. No arbitrary question, prompt, model or provider URL is accepted by the endpoint.