Player input and timing
Accepted buttons and axes, camera direction, held actions, action history, state age, and frame timing.
Production authority migration
Direct Slayer cutover
A conservative progress ledger for replacing the temporary player CAGE-authority path with Direct Slayer. Exact reverse engineering, clean code extraction, and production readiness are shown separately.
What is Slayer?
Slayer is New World’s player action and animation state machine. It decides what the character is doing now, whether a requested action is allowed, which animation should play, and which gameplay state must change with it. The original retail server participated in those decisions; Direct Slayer is our clean server-side reconstruction of that behavior.
This is a large port because Slayer is a coordinator, not an isolated animation player. Every state asks questions—called predicates—and runs ordered state changes—called reducers—across much of the game. We must reconnect those dependencies to authoritative server data, preserve their exact order and rollback together if any part fails. That is why the work is measured by complete authority boundaries rather than a raw function count.
Movement and physics
Walking, sprinting, dodging, facing, root motion, ground support, collision, water, traversal, mounts, and posture.
Combat and abilities
Attacks, block, aim, reload, stamina, cooldowns, ability phases, hit windows, and weapon-specific rules.
Character facts
Equipment, perks, status effects, grants, resources, interaction state, and other live gameplay conditions.
Animation state
Layers, selectors, families, tags, markers, playback time, transitions, and ordered Enter–Update–Exit callbacks.
Multiplayer publication
Atomic owner and observer updates, late join and reconnect state, rollback, and server-authoritative replication.
top-level blockers open
normalized unresolved owners
26 + 6
OnUpdate calls + inline groups
calls in bounded modules
Master census
These are different execution surfaces, not parts of one additive “call total.” In particular, 5,059 counts receiver bindings—not numbered OnUpdate calls.
Unresolved authority inventory
OnUpdate call chipaway
“Exact” means the complete reducer body is understood. “Bounded slice” means a proved route is implemented but other authoritative branches remain. Module extraction is architecture progress; it does not by itself close a production blocker.
Eight cutover blockers
This stable product ledger controls the readiness estimate. Nested implementation work is recorded inside a blocker until the complete authority boundary closes.