Tags
Creators
Details
2.0.0
Compatibility
Changes
Yay! A global update
Translations support, full redesign of all the commands and main infos, targets support, new flexible config, more control over who can use commands, new commands, code improvements.
- Potential support for other languages (we just need to start translating now)
- Overhauls and redesigns for every single command in the mod. This also includes /hc that prints useful information and command lists. Speaking of which, almost every single output is now interactable: tap to toggle command, change some config value, execute or suggest something, etc.
- Support for targets. This is huge, because now you can affect other players with Helpful Commands. For example, make them be able to fly, or make them invulnerable and vice versa. Also works with entities: for instance, /dimension command now allows you to switch dimensions for other entities, not just players.
- It is now possible to set OP level required to execute a certain command. For example, make /gm command only available for the most privileged people on your server, or make /feed command available to literally everyone!
- Rebased Helpful Commands config. You will have to reconfigure the mod again, but you will be surprised by how easy it is to do now. With lots of code improvements and optimizations, configuring the mod is not hard and annoying at all. That also makes it more flexible, allowing you to set /explosion command power limit to your own preferred value. And, of course, you can also set the required OP level to edit mod's config.
- Individual command improvements. /home and /back commands, for instance, now show a really neat position output, as well as provide you with interactable chat texts that you can click on.
- New /ignite command which allows you to set target(s) on fire for a specified number of seconds.
- Removed /abilities command in favor of /god and /fly. Hopefully, this makes things more user-friendly and easy.
- Code optimizations in the mod itself. Potentially makes it more readable, but feel free to propose improvements.
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:lIRUH8gT:B2R77LSh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lIRUH8gT:B2R77LSh"
}

