TriggerCheck
Staff-Initiated Triggerbot Detection for Minecraft Servers
Staff-Initiated Triggerbot Detection for Minecraft Servers
» What is TriggerCheck?
TriggerCheck is a lightweight staff-operated anti-cheat Skript that lets moderators
manually initiate a live triggerbot check on any online player — no third-party anti-cheat
subscription required. The suspect is silently or visibly teleported into a dedicated
test arena where a Citizens2 NPC is spawned directly in front of them. If the player
automatically attacks the NPC (as a triggerbot would), they are flagged, warned, and
automatically banned.
Built for PvP servers. Operated by staff. Zero false positives from automation.
» Features
- Staff Command Triggered — Run
/triggercheck <player>to instantly start a check on any online player - Automated NPC Arena — Builds a black concrete test room at configurable far-off coordinates, away from other players
- Citizens2 NPC Spawning — Spawns a real NPC with a configurable skin directly in front of the suspect
- Camera Lock — Forces the player's view direction toward the NPC — they cannot look away
- Movement Freeze — Prevents the suspect from moving during the check
- Hit Detection — Detects attack attempts, left clicks, and damage events; applies a cooldown to prevent spam counting
- Configurable Hit Threshold — Set how many hits = a flag (default: 2 hits within the check)
- Auto Ban on Flag — Executes a configurable-length tempban + permban automatically if flagged
- Timeout / Pass — If the player survives the full check time without hitting, they pass and are returned safely
- Silent Mode — Optionally hide what the check is from the suspect (shows generic "AntiCheat Review" instead of "TriggerCheck")
- Staff Broadcast — All staff with the permission node see real-time hit counts during every check
- Cancel Command — Any staff member can cancel an in-progress check with
/triggercheckcancel <player> - Status Command — Check who is currently being tested with
/triggercheckstatus - NPC Watchdog Loop — Automatically detects and recovers if the NPC entity goes missing mid-check
- NPC Health Guard — Continuously restores NPC health so it cannot be killed
- Arena Auto-Cleanup — The test arena is fully cleared after every check, win or lose
- Disconnect Handling — If the suspect logs off mid-check, staff are notified and cleanup runs automatically
- Sound & HUD Feedback — Configurable pass/fail/tick sounds and on-screen titles throughout the check
» Commands & Permissions
| Command | Description | Permission |
|---|---|---|
/triggercheck <player> | Start a triggerbot check on a player | triggercheck.use |
/triggercheckcancel <player> | Cancel an active check | triggercheck.use |
/triggercheckstatus | View who is currently being checked | triggercheck.use |
triggercheck.use— Allows staff to run and manage checkstriggercheck.bypass— Bypasses all check restrictions (give to admins/trusted staff)
» Requirements
- Skript 2.15+ — The core scripting engine
- SkBee 4.28+ — Required for advanced Skript functionality (scoreboard tags, vectors, etc.)
- Citizens2 — Required for NPC spawning and management
» Configuration
All settings are defined at the top of the script in the options block — no external config file needed. Key options include:
- Arena location — Set X/Z coordinates far from your main world (default: 500,000 / 500,000)
- Check timeout — How long a check lasts before the player automatically passes (default: 25s)
- Max hits — Number of hits required to flag a player (default: 2)
- Hit cooldown — Ticks between registered hits to prevent stacking (default: 6 ticks)
- Ban duration — How long the tempban lasts (default: 14 days)
- Ban reason — Customisable ban message shown to the player
- NPC skin — Set the in-game username whose skin the NPC will use
- Silent mode — Toggle whether the player sees "TRIGGERBOT CHECK" or a generic "AntiCheat Review"
- Sounds — Configurable pass, fail, and tick sounds
- Brand name — Customise the prefix shown in messages (e.g. AntiCheat)
» How It Works
1. Staff runs
/triggercheck <player>2. The script saves the suspect's location, gamemode, and rotation
3. A 5×5 black concrete arena is built at the configured far-world coordinates
4. The suspect is teleported into the arena in Adventure mode, frozen in place
5. Their camera is locked facing directly at the NPC position
6. A Citizens NPC with a custom skin is spawned 2 blocks in front of them
7. The check timer begins — hit detection, HUD display, and sound loops all start
8. If the player hits the NPC the configured number of times → flagged → auto-banned
9. If the timer expires with no flag → check passed → player returned to their original location
10. The arena is fully cleared regardless of outcome
» FAQ
Q: Will this ban players who accidentally click?
No. The default hit threshold is 2 hits and there is a per-hit cooldown to prevent accidental double-clicks from counting. You can raise the threshold in the config.
Q: Can the player escape the arena?
No. Barrier blocks surround the test area, movement is restricted to a 0.15 block tolerance, and the player is continuously teleported back if they drift. Inventory, chat, and commands are also locked during the check.
Q: What if the NPC dies or disappears?
A watchdog loop runs every 3 seconds to detect and recover the NPC entity. An NPC health guard loop also continuously restores its health to prevent it being killed.
Q: Can only one check run at a time?
Yes, intentionally. Simultaneous checks would conflict over the single shared arena location. The script blocks any new check while one is already active and tells staff who is currently being checked.
Q: What if the player disconnects?
The check is automatically ended, staff are notified, and the arena is cleaned up. No ban is issued on disconnect — that decision is left to staff.
Made by nbme · Skript resource for Minecraft Java Edition
If you find a bug or have a suggestion, leave a reply or open a conversation.
If you find a bug or have a suggestion, leave a reply or open a conversation.
