Tags
Creators
Details
4.7.2
Compatibility
Changes
This is to be considered a major version, because of the big changes i've done.
So please read carefully and do not just drag and drop the file
New Features:
- Team Bank. Teams can now deposit and withdraw money from the team bank
- Team Join Fee. an option can be enabled to allow team owners (and managers) to set a join fee, that will automatically taken from players upon accepting an invite
- Invites now send a message featuring buttons to accept/deny the invite
- invites can now be sent with just /team invite <name>
- there is a new option in the config to always open the team list GUI when using /team list
- The messages now use MineDown, being 100% customizable, and the config has a new format to help finding messages
- Players can now disable invites /invites <enable/disable>, so a player with disabled invites can't be invited in a team
- the chatspy command now has some alies to prevent other plugins overriding the command: /teamchatspy, /tchatspy
- Added 3 new perms for team managers: FEE (manage the join fee), DEPOSIT (deposit money into the team bank), WITHDRAW (withdraw money from the team bank)
Fixes:
- Message sent upon wrong usage of the allychat is now customizable in messages.yml
- Message sent upon wrong usage of the team create command is now customizable in messages.yml
- Switched to the paper integration of the command manager for better performance
- chat spy messages will no longer sent to discord while using DiscordSRV
- fixed an issue that would prevent the plugin to load when Vault was not installed
- fixed an issue in the team gui that would diplay the members line for each team member
- fixed an issue that would send the teleport confirmation message 2 times in some cases
- much more that i can't remember
TO UPDATE:
if you missed the latest beta version go check out the changelog for it, and be sure to change that option in the config for team echests, otherwise they won't work
Delete your config.yml file.
Delete your messages.yml file
i did not have enough time to migrate all the messages to the new format. They will work just fine, and you can use MineDown in any of them to have new features such as clicable buttons, hover text, etc. i will do it within the next versions, so you will be able to do copy and past them manually, or just regenerate the file.
SPIGOT IS NO LONGER SUPPORTED
Will i be affected? most probably not. Almost all the servers (checking from bstats) are using paper forks, that includes like Purpur, pufferfish, leaf etc. If you are not using paper, use it. it is just way more optimized and there is no reasons to use spigot anymore.
1.19.4+ ONLY FROM NOW ON
As for paper, also almost everyones uses at least 1.20, so i updated to the 1.19.4 api to have more features that can help me bring more to the plugin. if you are running an older version don't update the plugin as it won't work.
If you find any issue please report them on GitHub
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:wpXBRMRY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O5OQXCl8:wpXBRMRY"
}

