Tags
Creators
Details
1.2
Compatibility
Changes
[Added] - New command /vanish, which hides you from other players without OP and sends leave/join message
[Added] - New Kit System - Commands /kit save <kit>, /kit <kit> <player/all> and /kit delete <kit>. All the kits are saved in config.yml
[Added] - Command /enchant now supports @s @p @r @a
[Added] - Addition for invsee: /invsee <player> armor> which shows player's armor, but you can't interract with it.
[Work In Progress] In future i'm preparing to add "tab-complete-toggle" to turn off recommendiation for players in commands, so to find out players on server is hard.
[Work In Progress] I'm also planning on migrating kits from config to database. Reason is that kits in config slows starts/restarts of server.
[Known Issue] You can't put vanish on other players, only yourself.
[Known Issue] Some features of this plugin could be having problem with HrdaNick.
[Known Issue] You can't just use /kit <kit>, you need to write a player name.
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:oAjBZoeB:SCvbF2fE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oAjBZoeB:SCvbF2fE"
}

