Skip to content

FAQ

Jump to bottom
Maxime Tonie edited this page Apr 11, 2026 · 1 revision

FAQ

My trigger isn't firing. What do I check?

  1. Run /pt debug YourName and trigger the action in-game. If you see the packet in console, the plugin is sending it. If you don't see anything, PacketTrigger isn't intercepting that particular packet — the plugin might be using a different delivery method.

  2. Check /pt list — make sure the trigger shows a green checkmark (enabled).

  3. Double-check the placeholder field exactly matches the start of the message you saw in debug mode. It's case-sensitive.

  4. Check that packet-source matches — if the plugin sends a SYSTEM packet and you have packet-source: PLAYER, it won't match.

  5. Check your conditions — if any condition fails, the trigger skips silently.

  6. Check if the player is on cooldown — /pt clearcooldowns YourName to reset.

The trigger fires but I see it twice.

This usually means you have packet-source: BOTH (or the old setup with both SYSTEM and CHAT registered) and the plugin sends both types. Change to packet-source: SYSTEM which is correct for virtually all plugin messages.

Can players abuse a PLAYER source trigger by typing the placeholder in chat?

Yes, if you use packet-source: PLAYER without protection. Always add a permission field so only trusted players or systems can trigger it, and set a reasonable cooldown. If you don't actually need player chat triggering, stick with packet-source: SYSTEM which is completely safe.

%pt_triggerName_1% is showing blank in TAB.

The placeholder returns empty until the trigger has fired at least once for that player. It doesn't persist between server restarts. If it's blank after the trigger fires, make sure PlaceholderAPI is installed and that the trigger name in the placeholder exactly matches the config key.

Does this work on Spigot?

PacketTrigger is built against the Paper API and uses Adventure components which aren't available on Spigot. It requires Paper or a Paper fork.

Does this work on 1.18 or older?

No. The SYSTEM_CHAT packet type was introduced in 1.19. On older versions most plugin messages went through the CHAT packet, but the code is written for 1.19+ Paper.

Will this break when Minecraft updates?

PacketTrigger relies on ProtocolLib for packet interception, which handles Minecraft version compatibility. As long as ProtocolLib supports the new version, PacketTrigger should keep working. The packet extraction code has 4 fallback methods specifically to handle differences between versions.

I want to fire the trigger from another plugin, not from a packet.

Use /pt test <trigger> <player> [data...] from console or via RCON. You can call it programmatically using Bukkit.dispatchCommand(Bukkit.getConsoleSender(), "pt test ...").

Clone this wiki locally