1.3.1
Compatibility
Changes
New Stuff
-
Added Lightning Strike Ability (Look where you want and press the keybind)
-
Added the ability to turn invisible with the armor equipped
-
Added toggleable nametag visibility
Bug Fixes
-
Fixed some cooldown issues
-
Fixed where if you wanted to turn the nametag visibility back on, it wouldn't: The command was typed wrong
-
Fixed the names in the code for everything to work properly (hopefully..)
Known Issues
-
Spamming the keybind for an ability can make the ability happen multiple times and then causes the cooldown to be dramatically longer (At least that's what I've noticed) Example: Spamming Lightning strike keybind, making a lot of lightning strikes then having to wait a longer period of time before being able to use it again
-
Unequipping the armor while you have nametag visibility turned off will not turn nametag visibility back on. (You currently have to manually press the keybind to turn visibility back on before unequipping the armor)
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:s4DEPswy:G3yNboyl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s4DEPswy:G3yNboyl"
}

