fixed the /team GUI being incomplete in v4.x
to update, please delete your teamgui.yml file
Fixed warps not migrating correctly from v3.x to v4.x
(if you have already migrated and have issue with warps just run the migrator again and it will be fixed)
This version adds some new features and a lot of bug fixes!
- Added /team rename command
- Now banned prefixes/names are no longer case-sensitive
- Now min/max name length is not the same as prefix length, and can be modified in the config
- Now also prefixes can have colors and restrict the use of them by a permission
- Fixed a bug where the message sent upon leaving a team would not color the team name
- Fixed a bug that would display teams with colors in their name with the colors codes in command completions
- Fixed a bug that would not let players create a team if they didn't have color permission even when not using colors
- Fixed /team info command that would mess up teams name if colors are enabled
- Fixed a bug that would count color codes as string length in names and prefixes
- Fixed a bug that would display "not in team" in the prefix placeholder even if the player was in a team but the team had no prefix
- removed unnecessary logs when using cross-server
- Fixed a bug that would not update the online players in other servers while using cross-server
- Fixed a bug that caused teams command to fail if the team had colors in the name
- Fixed a bug that would let players hit allied/team members with arrow or tridents
Thanks to @onurbzxp and @DJKenduc for their reports on GitHub
You need to reset your config.
You need to reset your messages file. Otherwise you can add this at the end of the file:
team-name-change-successful: "&3Successfully changed team name to &6%TEAM%&3!"
team-tag-cannot-contain-colours: "&3Sorry, the team prefix cannot contain '&' or '#' characters."
do not directly update from v3.xx, check the changelog from v4.0.
- Added an option to restrict the use of color codes with a permission (check the config)
You need to reset your config. Otherwise you can add this at the level of team.create:
require-perm-for-color-codes: false
You need to reset your messages file. Otherwise you can add this at the end of the file:
use-colours-missing-permission: "&3You don't have the required permission to use color codes"
do not directly update from v3.xx, check the changelog from v4.0.
This version is production-ready, but the file is still marked as BETA since i didn't create the migrator for v3.x yet.
- Added support for Hex color codes (#ffffffWHITE)
if your not updating from v4.0.4-BETA you need to regenerate your config completely
do not directly update from v3.xx, check the changelog from v4.0 This version can be considered production-ready.
- Now you can use color codes in team name (check the config)
- some minor bug fixes
- modified config structure to make it easier to understand
You need to regenerate your config completely
do not directly update from v3.xx, check the changelog from v4.0 This version can be considered production-ready.
Now team creation can charge players game currency via Vault
Vault and an economy plugins are required to enable this feature
You need to reset your config. Otherwise you can add this at the end of the config file:
economy:
# Whether to enable economy (Vault is required)
enable: true
# The cost to create a team
team-create: 100.0
You need to reset your messages file. Otherwise you can add this at the end of the file:
not-enough-money: "&3You don't have enough money for this action. Required balance is: &6%MONEY%"
do not directly update from v3.xx, check the changelog from v4.0 This version can be considered production-ready.
fixed errors while using SQLITE/H2/PSQL and some minor issues.
do not directly update from v3.xx, check the changelog from v4.0
Removed unnecessary messages in console while using cross-server and some minor issues
don't update directly from 3.xx. read changelog from v4.0
Cross-Server Support!
This version finally adds support for multi-instance setups. You will need a MySQL/MariaDB database and optionally (for more performance) a Redis server.
THE CURRENT DATABASE SCHEMA ISN'T COMPATIBLE!!! While this version might be utilized for production, as i tested it a lot, you can't use data from previous versions. If you try you might permanently corrupt all data! (i will create a migrator in the next updates)
This version is almost a complete rewrite of the plugin, i fixed a lot of issues and i honesty don't remember them all, but here's all i can remember:
- Cross-Server support
- Now Allies and Enemies are considered "relations" between teams. Each team can add any other team as either Ally or Enemy, but they are considered so only if both teams have the same relation for each other
- PvP between allies is restricted
- Finally added allychat
- teamchat and allychat now support %TEAM% and %PLAYER% placeholders in the format
- new Lib for Folia support (coming in the next versions)
- /team ally/enemy remove commands will only show allied/enemies team in the suggestions (command completion)
- if an invite gets denied the sender will receive a notification
- A LOT of bug fixes and other small new features
To update you need to regenerate both your config.yml and messages.yml
If you find any issue with this version, or wish to see new features please open an issue on GitHub
commit: https://github.com/xF3d33/UltimateTeams/compare/main...cross-server
This new version adds the possibility to limit team members with a permission
ultimateteams.max_members.10
for example. As for the warps, you have the possibility to enable stack-members in the config so that the max members will be the sum of default-max-team-size plus the permission. refer to the config for more information.
Also i started to develop an API for the plugin, which is already included in this version. if you need more info on how to use it you can contact me on Discord (xF3d3).
You will need to regenerate your config for this version.
Added 2 new LuckPerms contexts:
- team-name (if not in a team returns null)
- is-team-owner
This build adds support for LuckPerms contexts
For now i just added is-in-team, which returs true or false.
I didn't test this version. If you can, try it and reach me out on Discord (xF3d3), even if it works, so i can directly add other contexts and publish the final version.
You need to regenerate your config
Thanks.
Fixed an error when a player damages an allied team player
First of all i wanted to thank you all for using my plugin
(100 downloads in only 2 days after months of inactivity..).
I tried this version and i think it's production ready, but i'll still flag it as beta since i'm starting to make big changes here and there.
as said before i'll bring a lot of new features in this 3.x version, so if you want to help me speed up the development process try this build and let me know on github/discord if you find any issue
this version adds/fixes:
- removed unnecessary messages in console for servers using SQLite (i still recommend to try MariaDB or at least H2)
- added not-in-team message in the /teamchat command
- fixed the /team setwarp command
- fixed some issues with the bedrock players manager (be sure you have floodgate api enabled and correctly configured)
Before you update
This is a first build of a new major version i'm developing, and it will bring a lot of new features.
As for all the ALPHA builds, i haven't tested them, so i highly recommend to try this on a test server first.
if you want to help me speed up the development process try this build and let me know on github if you find any issue
This version adds/fixes:
- An error if you use "/team" without any arg
- An error that might happen to some FloodGate users when a bedrock player connects
- An error if you use commands like "/team enemy" incorrectly
- fixed error when using /team
- added an option to change the shown text in placeholders when a player is not in a team
i didn't fully test this version, so please report any issue on GitHub page
fixed database realted issues
fixed huskhomes hook not working