Slash commands
| Command | Effect |
|---|---|
/nyx | Toggle the bot |
/nyx on, /nyx off | Explicit |
/nyx status | State, class, spec, switches, and why it is idle |
/nyx list | Loaded rotations, active one marked |
/nyx use <name> | Pick a rotation (case-insensitive) |
/nyx auto | Re-pick from class and talents |
/nyx cd | Toggle cooldown abilities |
/nyx combat | Toggle "only act in combat" |
/nyx reload | Re-read External/ from disk, no client restart |
CTRL-SHIFT-X is the panic key: it stops the bot and latches. Press it again to resume.
Diagnostics
These exist for verifying the engine against the client rather than for daily use, but they are the fastest way to find out whether something is your rotation or the engine underneath it.
| Command | Effect |
|---|---|
/nyx draw | Toggle the world overlay: rings, health bars, labels, line of sight |
/nyx units | Living units within 100 yards, nearest first |
/nyx los | Line of sight to nearby units, plus a ground-height check |
/nyx cam | Validate the client camera the overlay projects with |
/nyx checkproj | Compare the projection against the client's own nameplates |
/nyx calibrate | Check object-manager field offsets against the client's own API |
/nyx probe | Raw object-manager readout |
/nyx diff, /nyx diffobj | Snapshot an object and report which words changed |
/nyx camdump | Dump the camera struct with annotations |
/nyx calibrate grades each memory offset CONFIRMED, AMBIGUOUS or WRONG by comparing what the engine reads against what the client's own Lua API reports. If a rotation is behaving oddly after a client change, run that first: it will tell you whether the engine is still reading the right memory.