1.0.4
Compatibility
Changes
✅ Added $delay$ placeholder feature for delayed command execution across all command types (TIME, INTERVAL, WEEKLY, MONTHLY_DAY, GAME_TIME).
✅ Implemented cumulative delay system where multiple $delay$ commands execute sequentially with customizable delay intervals.
✅ Commands without $delay$ before delayed commands execute immediately, while those after delayed commands execute after all delays complete.
✅ Added comprehensive delay support with delay value specified in seconds via the delay configuration field.
✅ Delay feature works seamlessly with all existing placeholder replacements (%day%, %month%, %year%, %hour%, %minute%, PlaceholderAPI, etc.).
✅ Enhanced configuration flexibility with delay parameter available for all command types without any restrictions.
✅ Added detailed logging for delayed command scheduling and execution with timing information.
Example Configuration
Here's a practical example of using the new delay feature for a server restart countdown:
restart-countdown:
enabled: true # Set to true to enable
type: "TIME"
commands:
- "say Restart in 10 seconds"
- "$delay$ say Restart in 9 seconds"
- "$delay$ say Restart in 8 seconds"
- "$delay$ say Restart in 7 seconds"
- "$delay$ say Restart in 6 seconds"
- "$delay$ say Restart in 5 seconds"
- "$delay$ say Restart in 4 seconds"
- "$delay$ say Restart in 3 seconds"
- "$delay$ say Restart in 2 seconds"
- "$delay$ say Restart in 1 second"
- "$delay$ say Restarting server now!"
- "$delay$ restart" # Restart command will execute after all delays
time: "23:59" # Execute at 23:59 every day
delay: "1" # 1 second delay between each command
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:qFZbTPYs:tWXIJBlQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qFZbTPYs:tWXIJBlQ"
}

