Tags
Creators
Details
4.7
Compatibility
Changes
Added Team EnderChests!
This version is 99% production-ready but i marked it as beta while waiting for more tests and reported issues.
Teams can now have one or more shared enderchest (with variable size)
permission to use the echest: ultimateteams.team.echest
Team Echests are not compatible with cross-server yet
Admins can view, manage, delete, add, backup and rollback teams echests with their dedicated command **/teamadmin echest **
other fixes/additions:
- teams will now be updated even if there are no players online for cross-server setups that use REDIS (impossible with pluginmessage due to its limitations)
- teamchat spy messages will not be sent via discordsrv anymore
- invites now feature a clickable button for who receive it
- echests are updated real-time to prevent item dupes
TO UPDATE:
-
delete both your config.yml and messages.yml files
-
enable enderchest migration in the config, wait for the server to start, then disable it and restart again.
Thanks to dei0 for the echest system. check out his fork of ultimateteams, that features a slighly different team management (like upgrades for more members and warps)
INFORMATION REGARDING THE NEXT VERSION
in the next version i will convert the messages file to a new format, and it will be published probably within 2-3 days, so i wouldn't recommend you to change the messages file after it regenerates, since you will have to do it again.
i am also gonna add a little bank system, featuring only team balance for now, but with the future vision of adding an optional level system.
Optional dependencies
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:O5OQXCl8:RGbJLYcw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O5OQXCl8:RGbJLYcw"
}

