Links
Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 6 months ago
All versions
2.0.0
Release
PacketTrigger 2.0.06 months ago 93
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Required content
Any compatible version
Changes
Added
SEND_TITLEaction — send title and subtitle with configurable fade timesPLAY_SOUNDaction — play any Bukkit sound with volume and pitch controlPLAY_PARTICLEaction — spawn particles around the playerREPEATaction — run a set of actions multiple times with a configurable intervalRANDOMaction — pick one action at random from a list- Per-trigger
cooldown— prevent a trigger firing more than once per N seconds per player - Per-trigger
conditions— list of checks that must all pass for the trigger to fire - Per-trigger
permission— only fire for players with a specific permission - Per-trigger
enabledflag — disable without deleting - Per-trigger
packet-source— chooseSYSTEM,PLAYER, orBOTH - Math expressions via
{math:<expr>}in any action field - PlaceholderAPI expansion —
%pt_<triggerName>_<index>%works in any PAPI-compatible plugin /pt test <trigger> <player> [data...]command — fire triggers manually for testing/pt debug [player]command — toggle per-player packet logging/pt statsand/pt resetstatscommands — see trigger fire counts/pt togglecommand — toggle settings live without reloading/pt clearcooldownscommand — clear cooldowns per player or globally- Built-in player placeholders:
%player_health%,%player_level% - DataStore — remembers last fired data per player so PAPI expansion can read it
Changed
- Placeholder long-form changed from
%pg_<tag>_<n>%to%pt_<triggerName>_<n>% - Listener moved to
listenerpackage, cleaner project structure - Removed all BungeeCord chat component dependencies — now uses Adventure API exclusively
- ProtocolLib dependency updated to
net.dmulloy2:ProtocolLib:5.4.0(Maven Central)
Fixed
- Double-trigger bug when both SYSTEM_CHAT and CHAT packets fired for the same message
- Packet type check prevents player chat from matching SYSTEM-only triggers
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:RNXohnsX:zFmnnQ7D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RNXohnsX:zFmnnQ7D"
}

