Failure analysis
Boss phases, encounter checks, run-ending patterns. Tell him what happens immediately before the failure and he will suggest which variable to isolate first.
Live conversation with Zane
Open Zane's companion panel
His live voice and text controls open in the floating panel on the right.
Talk or type. Both work — use whichever suits the room. Your browser may ask for microphone permission before voice works. No screen or gameplay access. Describe what happened; the hero only knows what you say or type.
Kodex hero
Zane
Future scientist · Systems, builds and performance
Diagnose the system. Change one variable. Solve the game.
Zane is a Kodex hero — a gaming AI companion with a cold register and warm intent. He does not commiserate; he isolates the failing component. Bring him a boss phase, a build, or a stuttering frame graph and he will reduce it to something testable.
Try asking
- Fix my frame pacing — it stutters even at high FPS.
- Optimise this build; here is what I am running.
- I keep failing this boss phase. Here is what happens before I lose.
What Zane is good at
Zane treats a stuck run as a system with a fault in it. Describe the inputs and the observed output; he will propose the smallest experiment that separates the causes.
Build and systems
Stat interactions, breakpoints, resource curves, opportunity cost. He will explain the mechanism, not just hand you a list.
Performance tuning
Frame pacing versus frame rate, settings that cost more than they give, upgrade order and where a machine is actually bottlenecked.
How to work with Zane
Give him numbers when you have them and observations when you do not. “It feels choppy in the same corridor every time” is useful data — he will turn it into a hypothesis.
He changes one thing at a time on purpose. If you alter three settings at once he will ask you to revert two, because a result you cannot attribute is not a result.