1.1.0
Compatibility
Required content
Changes
🚀 Version 1.1.0 Update
✨ New Features
1. /run Command - Dynamic Command Execution (Level 2 Permission)
A new command execution tool that supports reading and executing commands from strings or variables.
Usage:
/run con [string]- Directly execute a string command/run var [variable_name]- Execute command stored in a variable
Examples:
/run con kill @s→ Executes/kill @s- Assuming variable
strhas valuekill @e /run var str→ Executes/kill @e
2. /if Command - Conditional Command Execution (Level 2 Permission)
Powerful conditional judgment system supporting multiple parameter combinations, executing different commands based on condition results.
Full Syntax: /if <condition> then <success_command> else <fail_command>
Condition Types:
con [boolean]- Use direct boolean valuevar [variable_name]- Use variable value as condition
Command Types:
con [string]- Execute string command directlyvar [variable_name]- Execute command stored in variable
Combination Examples: /if con true then con say Success else con say Failure /if var condition then var success_cmd else var fail_cmd /if con false then con gamemode creative else con gamemode survival
Simplified Version (no else branch): /if con true then con say Condition met /if var flag then var single_command
🎯 Use Cases
- Automation Scripts: Dynamically generate and execute commands
- Conditional Operations: Execute different operations based on game state
- Variable Control: Store commands in variables for flexible invocation
Update Notes:
- This update focuses on enhancing command flexibility and automation capabilities
- All new commands require level 2 operator permissions
- Variables must contain valid command strings to execute properly
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:LtnX1xvK:SMzc8TaR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LtnX1xvK:SMzc8TaR"
}

