Troubleshooting

Fast fixes

Most Axo Tales problems still collapse to a small set of root causes: the wrong jar, the wrong runtime config, a misunderstood workbench lane, or missing debug logs when someone says a spell "just feels off."

Multiple versions are loading

Symptom

The game behaves like an older build, or different testers swear they are on the same mod version but see different behavior.

Fix

Remove old AxoTales-*.jar files from C:\Users\<you>\AppData\Roaming\Hytale\UserData\Mods. If Windows refuses to delete one, the world is still running and holding the file open.

The live config does not match the guidebook

Symptom

Arcane Crystal density, Kudu spawn timing, or spell costs feel different from the docs.

Fix

The guidebook documents src/main/resources/server-config.json. Your live world may already own an older or hand-edited runtime server-config.json. Compare the two before changing code.

Spell behavior feels wrong or inconsistent

Symptom

Teleport timing feels late, a spell refuses to cast, Light Book never settles, or mana gating looks wrong.

Fix

Grab the persistent spellbooks-debug.log from the plugin data directory. Axo Tales logs item detection, stat snapshots, event routing, and final allow-or-deny decisions there.

Bench or recipe confusion after updating

Symptom

Players think recipes vanished because they are looking in the old generic Arcane bench path.

Fix

Axo Tales recipes now live in the runtime-injected Spellblades and Armor tabs on the Arcanist's Workbench. Point players there first.

Invalid config edits

Symptom

Manual edits leave weird negative numbers, impossible values, or malformed JSON.

Fix

server-config.json must stay valid JSON. Axo Tales sanitizes some bad numeric values toward safe defaults, but malformed JSON still has to be corrected manually.