- Forced PvP zones: team PvP can now be always-on in specific worlds or
WorldGuard regions
Inside these zones teammates can always hit each other, no matter what the
team's /team pvp toggle is set to.
* Set worlds in config.yml under settings.features.pvp.forced-pvp.
* For regions, use the WorldGuard flag: /rg flag <region> team-pvp allow
- All messages moved to their own messages.yml file. Every message can now be:
* turned on or off individually (enabled: true/false)
* shown in chat, on the action bar, or both
Your old custom messages from config.yml are copied over automatically the
first time the plugin starts on this version.
- A few messages that used to be locked in the code are now editable in
messages.yml.
- /dteam reload now also refreshes the forced PvP settings, so no full restart
is needed after changing them.
NOTES
- This is a drop-in update. Just replace the jar and restart once.
- After the first start, edit your messages in messages.yml (not config.yml).
YAML:settings: invite-expiry-seconds: 30 team-limit: 50 features: home: enabled: true pvp: enabled: true forced-pvp: enabled: false # Whole worlds where team PvP is always on (world names, case-insensitive). worlds: - "example_arena"
- Fixed a bug in cross-server setups where team chat messages were not showing up for the player sending them
- Optimized team chat to be database free, making chat delivery instant, lag-free, and highly responsive
- Optimized how teams update across servers so it reloads in the background instead of causing potential lag spikes or database locks
- Restricted the SQLite connection pool to prevent connection timeouts and database locked errors
Config Changes & Additions:
YAML:# Added under the 'messages:' section in config.yml: messages: pvp-cannot-hurt-teammates: '&cYou cannot hurt teammates.' permission-changes-saved: "&aPermission changes saved." switch-on: "&a&lON" switch-off: "&c&lOFF"
- The "You cannot hurt teammates" PvP message is now fully customizable in config.yml under messages
- Look for "pvp-cannot-hurt-teammates" in the messages section to change it
- Existing configs will be updated automatically with the new message key
- Added new placeholder %team_has_home% that returns true or false based on whether your team has a home set
- Added new placeholder %team_has_team% that returns true or false based on whether the player is in a team
- These placeholders work with PlaceholderAPI and can be used in plugins like DeluxeMenu to show different items based on team status
- Added migration support for Gerhart's DonutTeam plugin
- Place the old DonutTeam folder in your plugins directory and run /dteam migrate gerhart-donutteam to import all teams, members, and permissions
- All team homes, friendly fire settings, and member permissions are carried over during migration
- Fixed cross-server team home being lost after renaming a team
- Fixed /dteam info command now showing the server name for cross-server homes
