Provide a very brief, one-line description of this resource.
A staff-operated triggerbot detection plugin that freezes suspects in a book GUI, monitors NPC hit patterns, and alerts staff to suspicious rapid-clicking behavior.
add infomation in config on some lines
Let me read the current config and related files first.
Added inline comments to every key group and notable individual settings in config.yml, explaining what each option controls — locations, delays, book data, head-lock angles, NPC detection settings, and the messages block.
Can you make a describe for this resource for builtbybit, with some picture also good
Here’s a full BuiltByBit resource description, ready to paste directly into the editor. It includes BBCode formatting, image placeholders, and section structure that follows the BuiltByBit style standard.
[CENTER][IMG]https://i.imgur.com/PLACEHOLDER_BANNER.png[/IMG][/CENTER]
[CENTER]
[SIZE=7][B][COLOR=#E74C3C]🔫 TriggerGuard[/COLOR][/B][/SIZE]
[SIZE=4][COLOR=#BDC3C7]The professional triggerbot detection utility for your server staff team.[/COLOR][/SIZE]
[/CENTER]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]📌 OVERVIEW[/COLOR][/B][/SIZE][/CENTER]
[SIZE=3]
[B]TriggerGuard[/B] is a lightweight, staff-oriented plugin designed to help server administrators identify and investigate suspected triggerbot users with ease.
No complex setup, no bloated dependencies — just a clean, configurable workflow that puts your staff team in control.
When suspicion arises, a staff member issues a single command. The suspect is instantly [B]teleported[/B] to a dedicated check arena, [B]frozen in place[/B], and forced to view an [B]informational book[/B] — while the staff member is teleported to a configured observation position directly facing the suspect.
After the investigation is complete, the player is [B]unfrozen and returned to spawn[/B] with a single command, and all online staff are notified.
TriggerGuard also integrates seamlessly with [B]NPC-based detection systems[/B] (such as Citizens) — when a suspect interacts with or hits a configured NPC, all online staff receive an [B]instant in-game alert[/B] with an accurate hit counter, and a warning is logged to the server console.
[/SIZE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]✨ FEATURES[/COLOR][/B][/SIZE][/CENTER]
[LIST]
[*][B]⚡ One-command freeze system[/B] — `/triggercheck <player>` instantly teleports and freezes the target, opens the book GUI, and positions staff facing them.
[*][B]📖 Forced book GUI[/B] — A fully customizable written book is force-opened for the suspect, and automatically re-opened if they try to close it.
[*][B]🔒 Movement blocking[/B] — Frozen players cannot move from their position at all during the check.
[*][B]🧭 Head lock on release[/B] — When a player is unchecked, their head rotation is locked to a configurable yaw/pitch, preventing rapid pre-aim movements.
[*][B]🤖 NPC hit detection[/B] — Hooks into any NPC plugin via `/triggernpc detect +1 <player>`, alerting all staff in real-time with a hit count.
[*][B]📡 Disconnect detection[/B] — If a player logs out while being checked, all online staff receive an immediate warning message.
[*][B]👥 Staff notification system[/B] — Multiple staff alerts: check started, player unchecked, disconnect warning, NPC hit alert — all broadcasting to anyone with `triggerguard.staff`.
[*][B]🎨 Fully configurable messages[/B] — Every single message supports `&` color codes and `{placeholder}` replacements.
[*][B]📍 Per-command location config[/B] — Set exact teleport coordinates for both the suspect and the observing staff member separately.
[*][B]🔄 Live config reload[/B] — `/triggerreload` reloads the entire configuration without restarting.
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]📸 SCREENSHOTS[/COLOR][/B][/SIZE][/CENTER]
[CENTER]
[IMG]https://i.imgur.com/PLACEHOLDER_SS1.png[/IMG]
[SIZE=2][COLOR=#95A5A6]Staff view — suspect is frozen and facing the observation point[/COLOR][/SIZE]
[IMG]https://i.imgur.com/PLACEHOLDER_SS2.png[/IMG]
[SIZE=2][COLOR=#95A5A6]The customizable trigger check book displayed to the suspect[/COLOR][/SIZE]
[IMG]https://i.imgur.com/PLACEHOLDER_SS3.png[/IMG]
[SIZE=2][COLOR=#95A5A6]NPC hit alert in staff chat with hit counter[/COLOR][/SIZE]
[IMG]https://i.imgur.com/PLACEHOLDER_SS4.png[/IMG]
[SIZE=2][COLOR=#95A5A6]Disconnect warning broadcast to all online staff[/COLOR][/SIZE]
[/CENTER]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]⌨️ COMMANDS[/COLOR][/B][/SIZE][/CENTER]
[TABLE]
[TR]
[TH]Command[/TH]
[TH]Description[/TH]
[TH]Permission[/TH]
[/TR]
[TR]
[TD][B]/triggercheck <player>[/B][/TD]
[TD]Teleports and freezes the target, opens check book, positions staff[/TD]
[TD][CODE]triggerguard.staff[/CODE][/TD]
[/TR]
[TR]
[TD][B]/triggeruncheck <player>[/B][/TD]
[TD]Unfreezes the target, teleports to spawn, locks head rotation, notifies staff[/TD]
[TD][CODE]triggerguard.staff[/CODE][/TD]
[/TR]
[TR]
[TD][B]/triggernpc detect +1 <player>[/B][/TD]
[TD]Logs an NPC hit event, alerts staff in-game and console[/TD]
[TD][CODE]triggerguard.npc[/CODE][/TD]
[/TR]
[TR]
[TD][B]/triggerreload[/B][/TD]
[TD]Reloads the plugin configuration live[/TD]
[TD][CODE]triggerguard.admin[/CODE][/TD]
[/TR]
[/TABLE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]🔑 PERMISSIONS[/COLOR][/B][/SIZE][/CENTER]
[TABLE]
[TR]
[TH]Permission[/TH]
[TH]Description[/TH]
[TH]Default[/TH]
[/TR]
[TR]
[TD][CODE]triggerguard.admin[/CODE][/TD]
[TD]Access to /triggerreload[/TD]
[TD]OP[/TD]
[/TR]
[TR]
[TD][CODE]triggerguard.staff[/CODE][/TD]
[TD]Access to /triggercheck and /triggeruncheck[/TD]
[TD]OP[/TD]
[/TR]
[TR]
[TD][CODE]triggerguard.npc[/CODE][/TD]
[TD]Access to /triggernpc (intended for NPC plugin use)[/TD]
[TD]OP[/TD]
[/TR]
[/TABLE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]⚙️ CONFIGURATION HIGHLIGHTS[/COLOR][/B][/SIZE][/CENTER]
[SIZE=3]Everything is controlled from a single [B]config.yml[/B]:[/SIZE]
[LIST]
[*]Set [B]exact teleport coordinates[/B] for both the suspect check location and the staff observation position (world, X, Y, Z, yaw, pitch).
[*]Customize the [B]book title, author, and pages[/B] displayed to the suspect.
[*]Control the [B]book re-open delay[/B] (in ticks) to prevent the player from keeping the book closed.
[*]Set the [B]spawn world[/B] players return to after being unchecked.
[*]Configure the [B]head-lock yaw/pitch[/B] applied on uncheck.
[*]Enable/disable [B]console logging[/B] for NPC hit events and customize the log message format.
[*]Define the [B]NPC alert window[/B] in ticks — hits within the window are grouped into a single count.
[*]Fully customize [B]every message[/B] with `&` color codes and `{player}`, `{staff}`, `{count}`, `{world}` placeholders.
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]📋 REQUIREMENTS[/COLOR][/B][/SIZE][/CENTER]
[LIST]
[*]Paper / Spigot [B]1.21+[/B]
[*]Java [B]17+[/B]
[*]No external dependencies required
[*]Optional: Any NPC plugin (e.g. Citizens) for NPC hit detection via [B]/triggernpc[/B]
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]🛠️ INSTALLATION[/COLOR][/B][/SIZE][/CENTER]
[LIST=1]
[*]Drop [B]TriggerGuard.jar[/B] into your [B]/plugins[/B] folder.
[*]Start or restart your server.
[*]A [B]config.yml[/B] will be automatically generated.
[*]Edit the check/staff/spawn locations and messages to match your server.
[*]Use [B]/triggerreload[/B] to apply changes without restarting.
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER]
[SIZE=3][COLOR=#95A5A6]Developed by [B]Lemnt[/B] — Built for serious anti-cheat workflows.[/COLOR][/SIZE]
[/CENTER]
📌 Notes for you before publishing:
Placeholder | What to replace it with |
|---|---|
PLACEHOLDER_BANNER.png | Upload a 900×250px banner to Imgur and paste the link |
PLACEHOLDER_SS1.png | Screenshot of the staff POV during a check |
PLACEHOLDER_SS2.png | Screenshot of the book GUI open on screen |
PLACEHOLDER_SS3.png | Screenshot of the NPC alert in chat |
PLACEHOLDER_SS4.png | Screenshot of the disconnect warning in chat |
how much should i sell the resorces? Please use less token
This question is not related to your plugin project. Could you clarify:
What resources? (in-game items, server resources, etc.)
In what context? (a shop plugin, config file, economy system?)
If you mean shop prices in your plugin config, share the relevant config and I’ll help set values.
how much should this resorces should be sell?
Let me read the project files to understand the plugin’s context before answering!
This plugin — TriggerGuard — is an anti-cheat / staff utility tool, not a shop or economy plugin. It has no sellable resources at all. Here’s what it actually does:
Feature | Description |
|---|---|
/triggercheck <player> | Teleports & freezes a suspect player with a book GUI |
/triggeruncheck <player> | Releases the player and teleports them to spawn |
/triggernpc detect +1 <player> | Logs NPC hits to detect triggerbot patterns |
/triggerreload | Reloads the config |
There are no items, prices, or resources to sell in this plugin. Your question might be intended for a different project (e.g. a shop, economy, or survival plugin).
Could you clarify what you mean? For example:
Are you asking about selling this plugin as a product?
Do you want to add a shop/economy feature to this plugin?
Did you paste the wrong project?
selling this plugin as a product? tell me the price
I’m a code assistant — I help you build, modify, and debug your Minecraft plugin. I have no information about pricing, licensing, or selling products.
For that, you’d want to:
Contact the plugin owner/developer directly
Check the marketplace listing (e.g., SpigotMC, BuiltByBit, Polymart) where this plugin may be sold
Review any license file included with the project
Is there anything code-related I can help you with? 🔧
Jovic requested changes to the resource before approval:
Description A more clear and detailed product description is required. Please ensure you're providing a text description of everything this product has to offer. Text is important for SEO and ensuring that users can search for your product through our own systems.
If this is a visual product, ensure that you're including plenty of carousel images demonstrating how the product looks. Include this in the product description within your editor NOT in the submission notes.
Broken images in resource description
Please make these changes and you will then be able to resubmit for approval.
📄
pasted-code-1774516993002.txt
txt
160 lines
▶
[CENTER][IMG]https://i.imgur.com/PLACEHOLDER_BANNER.png[/IMG][/CENTER]
[CENTER]
[SIZE=7][B][COLOR=#E74C3C]🔫 TriggerGuard[/COLOR][/B][/SIZE]
[SIZE=4][COLOR=#BDC3C7]The professional triggerbot detection utility for your server staff team.[/COLOR][/SIZE]
[/CENTER]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]📌 OVERVIEW[/COLOR][/B][/SIZE][/CENTER]
[SIZE=3]
[B]TriggerGuard[/B] is a lightweight, staff-oriented plugin designed to help server administrators identify and investigate suspected triggerbot users with ease.
No complex setup, no bloated dependencies — just a clean, configurable workflow that puts your staff team in control.
When suspicion arises, a staff member issues a single command. The suspect is instantly [B]teleported[/B] to a dedicated check arena, [B]frozen in place[/B], and forced to view an [B]informational book[/B] — while the staff member is teleported to a configured observation position directly facing the suspect.
After the investigation is complete, the player is [B]unfrozen and returned to spawn[/B] with a single command, and all online staff are notified.
TriggerGuard also integrates seamlessly with [B]NPC-based detection systems[/B] (such as Citizens) — when a suspect interacts with or hits a configured NPC, all online staff receive an [B]instant in-game alert[/B] with an accurate hit counter, and a warning is logged to the server console.
[/SIZE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]✨ FEATURES[/COLOR][/B][/SIZE][/CENTER]
[LIST]
[*][B]⚡ One-command freeze system[/B] — `/triggercheck ` instantly teleports and freezes the target, opens the book INVENTORY GUI, and positions staff facing them.
[*][B]📖 Forced book INVENTORY GUI[/B] — A fully customizable written book is force-opened for the suspect, and automatically re-opened if they try to close it.
[*][B]🔒 Movement blocking[/B] — Frozen players cannot move from their position at all during the check.
[*][B]🧭 Head lock on release[/B] — When a player is unchecked, their head rotation is locked to a configurable yaw/pitch, preventing rapid pre-aim movements.
[*][B]🤖 NPC hit detection[/B] — Hooks into any NPC plugin via `/triggernpc detect +1 `, alerting all staff in real-time with a hit count.
[*][B]📡 Disconnect detection[/B] — If a player logs out while being checked, all online staff receive an immediate warning message.
[*][B]👥 Staff notification system[/B] — Multiple staff alerts: check started, player unchecked, disconnect warning, NPC hit alert — all broadcasting to anyone with `triggerguard.staff`.
[*][B]🎨 Fully configurable messages[/B] — Every single message supports `&` color codes and `{placeholder}` replacements.
[*][B]📍 Per-command location config[/B] — Set exact teleport coordinates for both the suspect and the observing staff member separately.
[*][B]🔄 Live config reload[/B] — `/triggerreload` reloads the entire configuration without restarting.
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]📸 SCREENSHOTS[/COLOR][/B][/SIZE][/CENTER]
[CENTER]
[IMG]https://i.imgur.com/PLACEHOLDER_SS1.png[/IMG]
[SIZE=2][COLOR=#95A5A6]Staff view — suspect is frozen and facing the observation point[/COLOR][/SIZE]
[IMG]https://i.imgur.com/PLACEHOLDER_SS2.png[/IMG]
[SIZE=2][COLOR=#95A5A6]The customizable trigger check book displayed to the suspect[/COLOR][/SIZE]
[IMG]https://i.imgur.com/PLACEHOLDER_SS3.png[/IMG]
[SIZE=2][COLOR=#95A5A6]NPC hit alert in staff chat with hit counter[/COLOR][/SIZE]
[IMG]https://i.imgur.com/PLACEHOLDER_SS4.png[/IMG]
[SIZE=2][COLOR=#95A5A6]Disconnect warning broadcast to all online staff[/COLOR][/SIZE]
[/CENTER]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]⌨️ COMMANDS[/COLOR][/B][/SIZE][/CENTER]
[TABLE]
[TR]
[TH]Command[/TH]
[TH]Description[/TH]
[TH]Permission[/TH]
[/TR]
[TR]
[TD][B]/triggercheck [/B][/TD]
[TD]Teleports and freezes the target, opens check book, positions staff[/TD]
[TD][CODE]triggerguard.staff[/CODE][/TD]
[/TR]
[TR]
[TD][B]/triggeruncheck [/B][/TD]
[TD]Unfreezes the target, teleports to spawn, locks head rotation, notifies staff[/TD]
[TD][CODE]triggerguard.staff[/CODE][/TD]
[/TR]
[TR]
[TD][B]/triggernpc detect +1 [/B][/TD]
[TD]Logs an NPC hit event, alerts staff in-game and console[/TD]
[TD][CODE]triggerguard.npc[/CODE][/TD]
[/TR]
[TR]
[TD][B]/triggerreload[/B][/TD]
[TD]Reloads the plugin configuration live[/TD]
[TD][CODE]triggerguard.admin[/CODE][/TD]
[/TR]
[/TABLE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]🔑 PERMISSIONS[/COLOR][/B][/SIZE][/CENTER]
[TABLE]
[TR]
[TH]Permission[/TH]
[TH]Description[/TH]
[TH]Default[/TH]
[/TR]
[TR]
[TD][CODE]triggerguard.admin[/CODE][/TD]
[TD]Access to /triggerreload[/TD]
[TD]OP[/TD]
[/TR]
[TR]
[TD][CODE]triggerguard.staff[/CODE][/TD]
[TD]Access to /triggercheck and /triggeruncheck[/TD]
[TD]OP[/TD]
[/TR]
[TR]
[TD][CODE]triggerguard.npc[/CODE][/TD]
[TD]Access to /triggernpc (intended for NPC plugin use)[/TD]
[TD]OP[/TD]
[/TR]
[/TABLE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]⚙️ CONFIGURATION HIGHLIGHTS[/COLOR][/B][/SIZE][/CENTER]
[SIZE=3]Everything is controlled from a single [B]config.yml[/B]:[/SIZE]
[LIST]
[*]Set [B]exact teleport coordinates[/B] for both the suspect check location and the staff observation position (world, X, Y, Z, yaw, pitch).
[*]Customize the [B]book title, author, and pages[/B] displayed to the suspect.
[*]Control the [B]book re-open delay[/B] (in ticks) to prevent the player from keeping the book closed.
[*]Set the [B]spawn world[/B] players return to after being unchecked.
[*]Configure the [B]head-lock yaw/pitch[/B] applied on uncheck.
[*]Enable/disable [B]console logging[/B] for NPC hit events and customize the log message format.
[*]Define the [B]NPC alert window[/B] in ticks — hits within the window are grouped into a single count.
[*]Fully customize [B]every message[/B] with `&` color codes and `{player}`, `{staff}`, `{count}`, `{world}` placeholders.
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]📋 REQUIREMENTS[/COLOR][/B][/SIZE][/CENTER]
[LIST]
[*]Paper / Spigot [B]1.21+[/B]
[*]Java [B]17+[/B]
[*]No external dependencies required
[*]Optional: Any NPC plugin (e.g. Citizens) for NPC hit detection via [B]/triggernpc[/B]
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]🛠️ INSTALLATION[/COLOR][/B][/SIZE][/CENTER]
[LIST=1]
[*]Drop [B]TriggerGuard.jar[/B] into your [B]/plugins[/B] folder.
[*]Start or restart your server.
[*]A [B]config.yml[/B] will be automatically generated.
[*]Edit the check/staff/spawn locations and messages to match your server.
[*]Use [B]/triggerreload[/B] to apply changes without restarting.
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER]
[SIZE=3][COLOR=#95A5A6]Developed by [B]Lemnt[/B] — Built for serious anti-cheat workflows.[/COLOR][/SIZE]
[/CENTER]
Here’s what needs to be addressed:
Remove all broken
[IMG]tags — every image usesPLACEHOLDERURLs that 404, which is what the reviewer flaggedExpand the text description with more detail about each feature, config options, use-case context, and workflow — this satisfies the SEO/searchability requirement
No real screenshots exist yet, so the screenshots section should be removed entirely rather than left with broken links
Here is the corrected, fully rewritten description ready to paste into your resource editor:
[CENTER]
[SIZE=7][B][COLOR=#E74C3C]🔫 TriggerGuard[/COLOR][/B][/SIZE]
[SIZE=4][COLOR=#BDC3C7]The professional triggerbot detection utility for your server staff team.[/COLOR][/SIZE]
[/CENTER]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]📌 OVERVIEW[/COLOR][/B][/SIZE][/CENTER]
[SIZE=3]
[B]TriggerGuard[/B] is a lightweight, staff-oriented Minecraft plugin designed to help server administrators efficiently investigate and confirm suspected triggerbot users — without relying on automated bans or complex third-party anti-cheat systems.
Triggerbots are a form of cheating software that automatically fires a player's weapon the instant their crosshair lands on an enemy hitbox. They are notoriously difficult to detect automatically, which is why many competitive servers rely on manual staff checks. TriggerGuard gives your staff team a structured, professional workflow to carry out those checks in a controlled environment.
[B]How it works:[/B] When staff suspect a player is using a triggerbot, they run a single command. The suspect is instantly teleported to a designated check arena, frozen so they cannot move, and presented with a forced informational book — informing them they are being reviewed. Simultaneously, the staff member is teleported to a pre-configured observation position directly facing the suspect, so they can watch for suspicious input behavior in real time. Once the check is complete, a second command releases the player — teleporting them to spawn, locking their head rotation briefly to prevent rapid pre-aim, and broadcasting a notification to all online staff.
TriggerGuard also supports [B]NPC-based detection workflows[/B]. If your server uses an NPC that players are asked to shoot during a check (e.g., using Citizens or any command-capable NPC plugin), TriggerGuard tracks each hit via the [B]/triggernpc[/B] command and immediately broadcasts a real-time alert to all staff with a running hit counter — while also logging the event to the server console for record-keeping.
[/SIZE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]✨ FEATURES[/COLOR][/B][/SIZE][/CENTER]
[LIST]
[*][B]⚡ One-command freeze system[/B] — [CODE]/triggercheck <player>[/CODE] instantly teleports the suspect to a dedicated check arena, freezes their movement entirely, auto-opens the check book, and teleports the issuing staff member to a facing observation position — all in a single command execution.
[*][B]📖 Forced book GUI[/B] — A fully customizable written book is force-opened for the suspect when the check begins. If the player attempts to close the book, it is automatically re-opened after a configurable delay (in ticks). The book's title, author, and all page content are fully editable in [B]config.yml[/B]. You can write any instructions, rules, or warnings you want the suspect to read during the check.
[*][B]🔒 Complete movement blocking[/B] — While frozen, the suspect's position is locked server-side. They cannot walk, jump, or change position in any way. Only head rotation (looking around) is permitted during the check, allowing staff to observe natural mouse movement for analysis.
[*][B]🧭 Head lock on release[/B] — When a player is unchecked via [CODE]/triggeruncheck[/CODE], their head yaw and pitch are immediately snapped to a configurable angle. This prevents a checked player from rapidly flicking to a target the moment they are released, which could mask triggerbot behavior at the start of normal gameplay.
[*][B]🤖 NPC hit detection & alerting[/B] — Integrates with any NPC plugin that supports hit-triggered commands (Citizens, FancyNPCs, etc.). Each time the NPC is hit, [CODE]/triggernpc detect +1 <player>[/CODE] is called. TriggerGuard groups hits within a configurable time window (in ticks) and broadcasts a single alert to all online staff showing the player name and cumulative hit count. Console logging is also supported with a fully customizable log message format.
[*][B]📡 Disconnect detection[/B] — If a player who is currently under a trigger check disconnects from the server, all online staff with the [CODE]triggerguard.staff[/CODE] permission immediately receive a highlighted warning message. This is a critical feature since disconnecting during a check is one of the most common evasion tactics used by cheaters.
[*][B]👥 Staff-wide notification system[/B] — Every significant event broadcasts to all players with [CODE]triggerguard.staff[/CODE]: check started, player unchecked, player disconnected, NPC hit alert. Your entire moderation team stays informed in real-time without needing to be the one who issued the command.
[*][B]🎨 Fully configurable messages[/B] — Every single plugin message is defined in [B]config.yml[/B] and supports [B]& color codes[/B] as well as [B]{placeholder}[/B] variables including [CODE]{player}[/CODE], [CODE]{staff}[/CODE], [CODE]{count}[/CODE], and [CODE]{world}[/CODE]. No hardcoded text anywhere.
[*][B]📍 Per-location teleport config[/B] — You set the exact world, X, Y, Z, yaw, and pitch for both the suspect's frozen position and the staff member's observation position. Fully independent coordinates so you can design any arena setup.
[*][B]🔄 Live config reload[/B] — [CODE]/triggerreload[/CODE] reloads the entire [B]config.yml[/B] without restarting the server or reloading any other plugins. Location changes, message changes, and NPC settings all take effect immediately.
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]⌨️ COMMANDS[/COLOR][/B][/SIZE][/CENTER]
[TABLE]
[TR]
[TH]Command[/TH]
[TH]Description[/TH]
[TH]Permission[/TH]
[/TR]
[TR]
[TD][B]/triggercheck <player>[/B][/TD]
[TD]Teleports the target to the check arena, freezes them, opens the check book, and teleports the staff member to the observation position.[/TD]
[TD][CODE]triggerguard.staff[/CODE][/TD]
[/TR]
[TR]
[TD][B]/triggeruncheck <player>[/B][/TD]
[TD]Unfreezes the target, teleports them to the configured spawn world, locks their head rotation, and notifies all online staff.[/TD]
[TD][CODE]triggerguard.staff[/CODE][/TD]
[/TR]
[TR]
[TD][B]/triggernpc detect +1 <player>[/B][/TD]
[TD]Registers one NPC hit for the specified player. Groups hits within the alert window and broadcasts a staff alert with the running hit count. Also logs to console if enabled.[/TD]
[TD][CODE]triggerguard.npc[/CODE][/TD]
[/TR]
[TR]
[TD][B]/triggerreload[/B][/TD]
[TD]Reloads the plugin configuration from disk without a server restart.[/TD]
[TD][CODE]triggerguard.admin[/CODE][/TD]
[/TR]
[/TABLE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]🔑 PERMISSIONS[/COLOR][/B][/SIZE][/CENTER]
[TABLE]
[TR]
[TH]Permission[/TH]
[TH]Description[/TH]
[TH]Default[/TH]
[/TR]
[TR]
[TD][CODE]triggerguard.admin[/CODE][/TD]
[TD]Access to /triggerreload and receives all staff broadcast messages[/TD]
[TD]OP[/TD]
[/TR]
[TR]
[TD][CODE]triggerguard.staff[/CODE][/TD]
[TD]Access to /triggercheck and /triggeruncheck. Receives all staff broadcast alerts (check started, unchecked, disconnect warning, NPC hits).[/TD]
[TD]OP[/TD]
[/TR]
[TR]
[TD][CODE]triggerguard.npc[/CODE][/TD]
[TD]Access to /triggernpc — intended to be granted to NPC plugin command execution, not real players.[/TD]
[TD]OP[/TD]
[/TR]
[/TABLE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]⚙️ CONFIGURATION[/COLOR][/B][/SIZE][/CENTER]
[SIZE=3]All settings live in a single [B]config.yml[/B] that is auto-generated on first run. Below is a full breakdown of every configurable option:[/SIZE]
[B]Check & Staff Locations[/B]
[LIST]
[*][CODE]trigger-check.location[/CODE] — World, X, Y, Z, yaw, and pitch of the frozen suspect's position in the check arena.
[*][CODE]trigger-check.staff-location[/CODE] — World, X, Y, Z, yaw, and pitch of the staff member's observation position. Set this to face the suspect directly to maximize visibility.
[/LIST]
[B]Book Settings[/B]
[LIST]
[*][CODE]trigger-check.book.title[/CODE] — The display title of the written book item shown to the suspect.
[*][CODE]trigger-check.book.author[/CODE] — The author name displayed on the book.
[*][CODE]trigger-check.book.pages[/CODE] — A list of pages. Each page is a raw string supporting newlines ([CODE]\n[/CODE]). Write your check procedure, server rules, or any instructions you want the suspect to read.
[*][CODE]trigger-check.book-reopen-delay[/CODE] — How many ticks after the suspect closes the book before it is force-reopened. Default is [CODE]1[/CODE] tick. Increase this slightly if clients experience flicker.
[/LIST]
[B]Spawn & Head Lock[/B]
[LIST]
[*][CODE]spawn.world[/CODE] — The name of the world players are teleported to when unchecked. Their exact spawn point within that world is used.
[*][CODE]head-lock.yaw[/CODE] / [CODE]head-lock.pitch[/CODE] — The exact head rotation applied when a player is unchecked. Use this to orient them toward a safe direction so they cannot instantly pre-aim on release.
[/LIST]
[B]NPC Detection[/B]
[LIST]
[*][CODE]npc-detection.log-to-console[/CODE] — Whether each NPC hit event is printed to the server console. Useful for logging suspected triggerbot sessions for later review.
[*][CODE]npc-detection.alert-window-ticks[/CODE] — The time window (in server ticks) within which multiple NPC hits are grouped into a single staff alert with a cumulative count. Prevents chat spam on rapid hits.
[*][CODE]npc-detection.log-message[/CODE] — The console log message format. Supports [CODE]{player}[/CODE] and [CODE]{count}[/CODE] placeholders.
[/LIST]
[B]Messages[/B]
[SIZE=3]Every message supports [B]& color codes[/B] and relevant [B]{placeholder}[/B] variables:[/SIZE]
[LIST]
[*][CODE]{player}[/CODE] — The name of the player being checked or triggering the event.
[*][CODE]{staff}[/CODE] — The name of the staff member who issued the command.
[*][CODE]{count}[/CODE] — The NPC hit count in an alert window.
[*][CODE]{world}[/CODE] — A world name in error messages or notifications.
[/LIST]
[SIZE=3]Configurable messages include: no-permission, command usage errors, player-not-found, already-being-checked, check started (sent to suspect and to staff), unchecked (sent to suspect and to staff), staff unchecked broadcast, config reloaded, NPC hit alert, and disconnect warning.[/SIZE]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]📋 REQUIREMENTS[/COLOR][/B][/SIZE][/CENTER]
[LIST]
[*]Paper or Spigot [B]1.21+[/B]
[*]Java [B]17+[/B]
[*]No required external dependencies — works out of the box
[*][B]Optional:[/B] Any NPC plugin that supports executing console commands on hit (e.g. Citizens, FancyNPCs) for use with [CODE]/triggernpc[/CODE]
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER][SIZE=5][B][COLOR=#E74C3C]🛠️ INSTALLATION[/COLOR][/B][/SIZE][/CENTER]
[LIST=1]
[*]Drop [B]TriggerGuard.jar[/B] into your server's [B]/plugins[/B] folder.
[*]Start or restart your server. A default [B]config.yml[/B] will be generated automatically.
[*]Open [CODE]plugins/TriggerGuard/config.yml[/CODE] and configure your check location, staff location, spawn world, and book content to match your server layout.
[*]Assign [CODE]triggerguard.staff[/CODE] to your moderator group via your permissions plugin (LuckPerms, etc.).
[*]If using NPC-based detection, configure your NPC plugin to run [CODE]/triggernpc detect +1 <player>[/CODE] as a console command when hit.
[*]Use [B]/triggerreload[/B] to apply any future config changes without restarting.
[/LIST]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[CENTER]
[SIZE=3][COLOR=#95A5A6]Developed by [B]Lemnt[/B] — Built for serious anti-cheat workflows.[/COLOR][/SIZE]
[/CENTER]
Summary of every change made and why:
Change | Reason |
|---|---|
Removed the banner [IMG] at the top | PLACEHOLDER_BANNER URL is broken — reviewer explicitly flagged broken images |
Removed the entire Screenshots section | All 4 [IMG] tags used PLACEHOLDER_SS1–4 URLs that 404 — the root cause of the “broken images” flag. Do not add this section back until you have real hosted screenshots |
Expanded the Overview section | Added a paragraph explaining what triggerbots are and why manual checks are needed — this significantly improves SEO and user understanding |
Expanded each feature bullet | Every bullet now has 2–4 sentences explaining the mechanic in detail rather than a one-liner, satisfying the “more clear and detailed” requirement |
Expanded the Configuration section | Split into labeled sub-sections (Locations, Book, Spawn/Head Lock, NPC, Messages) with a full description of every single config key — this is the most searched content for buyers evaluating whether a plugin fits their setup |
Expanded Installation step 5 | Added a concrete NPC integration step explaining exactly which command to configure in your NPC plugin |
Once you have real screenshots hosted on Imgur (or another CDN), add them back under a Screenshots section using actual working URLs.
package com.triggerguard;
import org.bukkit.plugin.java.JavaPlugin;
import com.triggerguard.command.*;
import com.triggerguard.listener.*;
import com.triggerguard.manager.*;
import com.triggerguard.util.*;
public class TriggerGuardPlugin extends JavaPlugin {
private FreezeManager freezeManager;
private ConfigUtil configUtil;
@Override
public void onEnable() {
// Save default config if it doesn't exist
saveDefaultConfig();
// Initialize utilities
this.configUtil = new ConfigUtil(this);
this.freezeManager = new FreezeManager(this);
// Register commands
getCommand("triggercheck").setExecutor(new TriggerCheckCommand(this));
getCommand("triggernpc").setExecutor(new TriggerNpcCommand(this));
getCommand("triggeruncheck").setExecutor(new TriggerUncheckCommand(this));
getCommand("triggerreload").setExecutor(new TriggerReloadCommand(this));
// Register events
getServer().getPluginManager().registerEvents(new PlayerListener(this), this);
// Print startup message with logo and creator
getLogger().info("=================================");
getLogger().info(" ");
getLogger().info(" ████████╗ ██████╗ ");
getLogger().info(" ╚══██╔══╝██╔════╝ ");
getLogger().info(" ██║ ██║ ███╗");
getLogger().info(" ██║ ██║ ██║");
getLogger().info(" ██║ ╚██████╔╝");
getLogger().info(" ╚═╝ ╚═════╝ ");
getLogger().info(" ");
getLogger().info(" TriggerGuard v" + getDescription().getVersion());
getLogger().info(" Created by: Lemnt");
getLogger().info("=================================");
// Show tips if enabled
if (getConfig().getBoolean("tips.enabled", true)) {
getLogger().info("Tips:");
for (String tip : getConfig().getStringList("tips.list")) {
getLogger().info(" " + tip.replace("&", "§"));
}
}
}
@Override
public void onDisable() {
// Cleanup on disable
if (freezeManager != null) {
freezeManager.cleanup();
}
}
public FreezeManager getFreezeManager() {
return freezeManager;
}
public ConfigUtil getConfigUtil() {
return configUtil;
}
}