Dodge Terraria bosses with typed reflexes

01 · Role in the system

What Jev does here

Jev answers five parallel questions at 5Hz: a Choice among nine intents - keep, back, close, evade, up, float, grapple, orbit, dive - a five-band danger score, and Nouls for dash and jump. The reflex layer owns everything per-frame: aiming, distance keeping, dash double-tap timing, grapple anchor search, the one-frame jump release, and expiry fallbacks for stale intents. Each boss's playbook is a piece of prose in BossBook.cs rather than a branch tree - how the fight goes, what the arena looks like, which intents to disable, what distance to hold - so adding a boss is adding a text entry, and a switch can ablate the book to measure what the knowledge is worth. The author reports it beating every pre-hardmode boss on Master Mode, with bilibili and YouTube recordings linked from the repository; the mod falls back to a conservative baseline without an API key.

A 5Hz brain over a 60fps body

The rate split is the design: every 200 milliseconds, one batched request asks a nine-way intent Choice, a five-band danger Score, and dash/jump Nouls; per-frame work — aiming, distance keeping, double-tap timing, grapple anchors, the one-frame jump release, stale-intent expiry — belongs to deterministic reflex code. The model picks the fight's direction five times a second; the hands execute at frame rate.

Boss knowledge is prose, not branch trees: each boss's playbook is a text entry in BossBook.cs describing the fight, the arena, which intents to disable, what distance to hold. Adding a boss is adding a paragraph — and a switch can ablate the book entirely to measure what the written knowledge is worth.

Master Mode wins, with the fine print attached

The author reports beating every pre-hardmode boss on Master Mode, with bilibili and YouTube recordings linked from the repository — the strongest game-cluster claim in the index, carried with its caveats: the project was developed entirely with AI assistance, the full-game walkthrough runs with a helper mod active, and arbitrary world seeds are not guaranteed because the author fixes structural failures rather than patching per-seed.

Without an API key the fight layer falls back to a conservative baseline, so the Jev-driven mode and the fallback are cleanly distinguishable — which is exactly what a reproduction of this record should measure first.

02 · Control boundary

Where Jev sits

Game state goes out as one batched 5Hz request - intent Choice, danger score, dash and jump Nouls; deterministic reflex code owns aiming, timing, TTLs, and keys.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

• The README states the project was developed entirely with AI assistance, and the full-game walkthrough pipeline runs with the DragonLens helper mod active; boss-fight recordings are on Master Mode.
• The walkthrough is not guaranteed on arbitrary world seeds; the author fixes structural failures rather than patching per-seed.
• Without an API key the fight layer falls back to a conservative baseline, so Jev-driven dodging is not demonstrated in that mode.

04 · Attribution

Public sources

This is a Community record: the project was published by a third-party community author.

• Reisenbug ↗Community · github · public · checked 2026-09-20