0.0.2
Compatibility
Changes
Breif Sumary
Deleted Fly Command Deleted Short Grass Given??? Fixed Nuke Rules to Acctauly Work Bomb Command Bugs Fixed Made Nuke Circular instead of Square
Information
Current Commands: /nuke <x> <y> <type> /bomb /nukerule <rule> <value>
Nuke tupes: strike(Destroys Evyerhting -60 to 350) nuke(wide radius of bombing)
Nukerules: strikeTNT(amount of tnt when using strike) nukeTNT(amount of tnt when using nuke)
Extra & Credits
Planed(Ordered from importancy):
- Able to change bomb strength
- Tool to bomb from clicking
- Able to increase nuke radius
- Strike a nuke or a strike where your looking
- Able to make it just explosion instead of tnt
Additional Notes: Sorry for how long it took i accidently deleated the file and had to find how to reuse the jar Might lag because it uses sin and cos inorder to determine where the tnt should go I have been working on a seperate project for my friend's server
Thank your for your patience!
Made by ShkllgodTrueGod also known as shkllgod
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:hsNVvJR1:gN9U4tSr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hsNVvJR1:gN9U4tSr"
}

