Tags
Creators
Details
1.1-1.21.1
Compatibility
Changes
v1.1 - 2025-09-01
Status: Release-Candidat (RC)
Overview
Plugin: FootstepsFX
Autor: Wolfwriter
Short Description: Players leave a configurable particle trail as they run.
Added
Lock/Unlock system for effects per player Players can lock or unlock individual particle effects.
- /trail lock effect - (Permission: trail.lock)
- /trail unlock effect - (Permission: trail.lock)
- /trail lock player effect - (Permission: trail.lock)
- /trail unlock player effect - (Permission: trail.lock)
Global lock/unlock of all effects
- /trail lock effect all or *
- /trail unlock effect all or *
- also for other players via player effect all
New commands:
- /trail reload – reloads all saved data (Permission: trail.reload)
- /trail help – displays all available commands and their descriptions
Tab completion for all new commands
- Suggestions for effect, player and particle types
- Dynamically dependent on argument position
Effect validation
- Invalid effect names are recognized and intercepted with a message
- /trail list provides valid options
Changed
CommandHandler extended
- Structure for subcommands modularized
- Player verification and UUID access unified
- Error messages and usage notes improved
Fixed
MC compatibility clarified:
- Plugin is now optimized exclusively for Paper 1.21.1
- No longer compatible with other 1.21.x variants
Performance
- No additional performance changes in this version
- Existing optimizations from v1.0 remain unchanged
Data & Configuration
New keys:
{
"uuid-of-player": {
"enabled": true,
"effectType": "flame",
"intensity": 8
“lockedEffect”: [],
“unlockedEffects”: []
}
}
Kompatibilität
MC-Versionen: ab 1.21 Plattformen:
- Paper: 1.21.1
Known issues
- Lock/Unlock only works on Particle effects with Void.class as the data type
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:UsKFUCNA:fFLCAEox"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UsKFUCNA:fFLCAEox"
}

