0.2.0
Compatibility
Changes
About the update
This update adds a few basic commands and one advanced command. Most commands have the Entity.Player parameters, "target_player" and "source_player". This update is also available for Neoforge 1.21.1. It isn't recommended that you use this in 1.20.2+. Check out changes in "THE BAD NEWS AND GOOD NEWS" section 3 of every mod update.
What's in the update?
The update has a few commands. All Command Utility commands start with "comutil". For example, (this exists) "/comutil:example_command". The commands for this update is: (Please note that you MUST use "comutil:" for the beginning of the command.)
- enable_player_can_fly (Creative mode releated)
- disable_player_can_fly (Creative mode releated)
- enable_player_can_be_damaged (God Mode Related)
- disable_player_can_be_damaged (God Mode Related)
- enable_player_can_build (Adventure mode related)
- disable_player_can build (Adventure mode related)
- self_destruct_no_selfkill (Explode without dying.)
The bad news and good news
- The good news
All commands are limited to OP Level 4, which means only operators (OP) can use it.
- The BAD news
self destruct command gives you a 4 second invurnability mode, allowing you to survive a 255 sharpness sword/axe or 255 density mace after self destruction.
The command can also be BUGGED. Sometimes you DON'T get invurnability if you run the command too many times.
NeoForge is a forked version of forge and forge is a nerfed version of NeoForge. The forge version of the mod (this one) was transfered from a NeoForge build to a Forge build, this could mean that some features may not work since I do not have the time to test it and I need it to release a bit quick.
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:rhQVeg1d:QhWZjPIl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rhQVeg1d:QhWZjPIl"
}

