Tags
Creators
Details
2.1
Compatibility
Changes
You can now transfer vanilla enderchest to EnderEX chest via the command /enderex transfer <player>
if you wanna force the transfer, even if the player already has items in his EnderEX chest, you can do /enderex transfer <player> force
The player HAS to be online for it to work.
Keep in mind, the transfer will always abort if the player has less than 3 rows in his EnderEX chest (so enderex.chest.3 permission minimum)
I also added an option to do it on player login, same limitations, it will not overwrite if the player already has items in his EnderEX Chest, but if you recently added the plugin and you need to migrate players chests, that's the automated way to do it.
New option : you can disable the physical replacement of enderchest in the options, if you disable it, the player will have access to his vanilla enderchest when he opens it, but will access the EnderEX chest when doing the command.
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:qTybaMX6:dfZwOxQT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qTybaMX6:dfZwOxQT"
}

