BotCheck
Fair-play verification: a check occasionally interrupts monster hunting to confirm a human is at the keyboard. Failing it repeatedly bans the account — right now a flat 1-day ban from the 10th failure (a temporary soft mode); the stricter ladder is dormant.
⏰ When it triggers#
| Chance per monster kill | 5% |
| Minimum gap between checks | 30 minutes |
📜 What happens#
- Your position is saved and you are warped to a holding area
- Movement, skills, item use and commands are all blocked until you answer
- Pass, and you return to exactly where you were
Logging out does not cancel a check — it is flagged on your account and waits for you. Answer it.
🎯 The challenge#
- The odd NPC — a ring of 8 NPCs, one of them different. Click it.
- The Item ID — 30 item icons, all the same item except one. Type that odd item's Item ID.
The pairs are near-identical look-alikes (5581 and 5582, 1686 and 1687, 12030 and 12031), so do not squint at the pictures: right-click the icons to read their Item ID. That is the intended solution — reading item information is exactly the human behaviour the check tests for.
One free miss at each stage; a second miss is a failure. It never fires in towns, instances, castles, near an MVP, or while AutoCombat is running.
⚠️ Failing#
Failures accumulate on your account; the count is cleared on the 1st of each month.
| Failure | Penalty |
|---|---|
| 1st to 9th | Warning, then warped back · no ban |
| 10th and every one after | 1-day account ban |
Temporary soft mode. Bot Check was log-only from 20 September; it is armed again with this flat rule. The old ladder — warning, then 1 day, 7 days, 30 days, a year — is dormant, not deleted, and can come back; there is no date for it.
- No mutes — muting does nothing to an unattended client.
- No answer within 60 seconds is a timeout: you are kicked, and it is not counted as a failure.
- Do not leave your character killing monsters unattended all the same — a check you are not there to answer ends your session.
🤖 Identity#
Hardware identity comes from NoxShield, the server's single source for it. An unknown hardware ID is never treated as a match for anything — failing to identify is not evidence of wrongdoing.
💡 If you get stuck#
Every check is logged as a pass, fail or timeout. If one genuinely breaks and leaves you frozen, a GM can clear it and return you to your save point — contact staff rather than waiting it out, because the block does not lift on its own.