Skip to content

ZelTeams

Configuration

Licensing

In the configuration, you can choose the license provider with:

license-key: INSERT YOUR LICENSE KEY HERE

license-provider: <Zeltuv|Pikz>

This option lets you use a license key generated either by our system or by Pikz Studios' system, depending on whether you got the plugin from a setup or not.

Team GUI Command

team-commands:

  • Specifies the commands used to open the Team GUI, which allows players to manage teams.
    • Default Commands:
      • team
      • teams
    • Customization: You can change these commands to any value you prefer.

Team Chat Command

teamchat-command:

  • Specifies the command used to send messages exclusively to team members.
    • Default Command: teamchat
  • Subcommand: team chat is also available as /team chat <message> (aliases /team c, /team tc), or /team chat alone to toggle it on/off. The subcommand name and aliases can be changed under team-subcommand.chat.
    • Customization: You can change this command to any value you prefer.

Ally Chat Command

allychat-command:

  • Specifies the command used to send messages to both team members and allies.
    • Default Command: allychat
    • Customization: You can change this command to any value you prefer.

Plugin Reload Command

teamreload-command:

  • Specifies the command used to reload the plugin's configuration and settings without restarting the server.
    • Default Command: teamreload
    • Customization: You can change this command to any value you prefer.

Admin Command

teamadmin-command:

  • Specifies the command used for administrative tasks, such as inspecting teams, modifying settings, or managing players.
    • Default Command: teamadmin
    • Customization: You can change this command to any value you prefer.

Banned Keywords Settings

banned-keywords: Controls restricted team names

  • List words that players cannot use in team names
  • Helps maintain appropriate team naming

Bank Balance Settings

return-balance-on-disband: Controls what happens to team money when a team gets disbanded.

  • Set to true: Money returns to the team owner.
  • Set to false: Money is deleted.

Message Callback Settings

If you are wondering what a message callback is, it's basically when you are asked for an answer in chat by the plugin, you can define the timeout and the cancel phrase.

lifetime:

  • Sets the duration (in seconds) that players have to respond to a question asked in the chat. After this time elapses, the question will expire.

cancel-phrase:

  • Specifies the word or phrase that players need to type in the chat to cancel the question. This allows players to opt out of responding if they choose.

Money Decimals Formatting

money-decimals:

  • Configures the display format for large monetary values (thousands, millions, and billions). Use the placeholder %number% to represent the numerical value.
    • Example for Thousands:
      • thousand: %number%K
      • This would display 1000 as 1K.
    • Example for Millions:
      • million: %number%M
      • This would display 1,000,000 as 1M.
    • Example for Billions:
      • billion: %number%B
      • This would display 1,000,000,000 as 1B.

Invite Lifetime

invite-settings:

  • Determines the validity period (in seconds) for team and ally invites. Once the specified time elapses, the invite will automatically expire.
    • Example:
      • If set to 300, invites will expire after 5 minutes.

Teleportation Timer

teleportation-timer:

  • Specifies the time (in seconds) required for a player to teleport back to their team's home. This adds a delay to teleportation, making it more strategic.
    • Example:
      • If set to 10, players will wait 10 seconds before teleporting.

Team Tag

max-length:

  • Defines the maximum number of characters allowed for a team's tag.

change-cooldown:

  • How long a team waits between tag changes. Use a duration  '1h', '12h', '2d' (d=days, h=hours, m=minutes, s=seconds). Default '1h' (enabled). Set to '0' or empty to disable.

change-cost.enabled:

  • Require a payment to change the tag. Requires Vault + an economy plugin; if either is missing the change is free (the plugin still works normally).

change-cost.amount:

  • The cost (default 1000.0).

Toggle/Untoggle features

Our plugin is designed to work well for most servers, but we understand that server owners have different preferences. That's why we've included a toggle-features section in the settings that lets you easily enable or disable specific features according to your server's needs.

  • *Features that can be disabled or enabled are: **Team Enderchest, Team Bank, Team Home, Alliances, Leaderboard, Economy-related features in general

Features:

  • This section allows you to enable or disable specific features of the plugin.
    • Options:
      • true: Enables the feature.
      • false: Disables the feature.

Team Home Settings

Teams can have several homes, set / teleported to / deleted from the Home menu (/team home → "Set Home" prompts for a name). The number of homes a team may have is set by the owner's permission team.home.<amount> (default 1); this value is stored so it stays correct even while the owner is offline. (Refreshed upon the owner’s join)

max-y-level-enabled:

  • Determines whether there is a maximum Y-coordinate restriction for setting team homes.
    • Options:
      • true: Enables the maximum vertical level restriction.
      • false: Disables the restriction, allowing team homes to be set at any height.

max-y-Level:

  • Specifies the maximum Y-coordinate at which a team home can be set. This setting is only active if max-y-level-enabled is set to true.
    • Default Value: 100
    • Example: If set to 100, players cannot set a team home above Y-level 100.

Team Creation Settings

requires-payment:

  • Determines whether players must pay a fee to create a team.
    • Options:
      • true: Enables the payment requirement.
      • false: Disables the payment requirement, allowing free team creation.

payment-amount:

  • Specifies the amount of in-game currency required to create a team. This setting is only active if requires-payment is set to true.
    • Default Value: 100.0
    • Example: If set to 100.0, players must pay 100 units of currency to create a team.

Team Colors

team-colors lets each team pick a color shown in their Settings menu (Settings → Team Color). Each entry has:

  • name — display name in the GUI
  • material — the icon material in the picker
  • color — the actual color code (legacy & codes or &#RRGGBB hex)
  • permission — optional; leave empty for free, or set a node like zelteams.color.red to lock the color behind a permission

12 colors ship by default (red and dark_red are permission-locked as examples). The selected color is exposed to other plugins via %zelteams_color%.

Color Revalidation (temporary ranks)

team-color-revalidation (default false) — when enabled, the team owner's permission for the currently selected color is re-checked every time they join. If the permission is gone (for example a temporary VIP rank expired), the team color resets to default and the owner is notified (message editable in the messages file). Only colors that have a permission set are affected. Note: if the rank expires while the owner is online, the reset happens at their next login.


Team Role Settings

What is a role?

A role is basically the rank of the player in your team; it allows your players to have a hierarchy system in their team.

How does the role priority work?

Roles are organized by priority, which determines their position in the team hierarchy. A higher priority number indicates a higher rank. For example, a role with priority 10 is higher than a role with priority 2.

⚠️ Reminder ⚠️

The roles with priority 1 and -1 are mandatory; if you remove them, you will break your data. Please do not do that.

The -1 represents the owner role and the 1 represents the default role.

Here’s an example of the configuration for it

Team-Roles:
  '-1':  # MANDATORY ROLE
    name: Recruit
    permissions:
      - USE_HOME
  '1':  # # MANDATORY ROLE
    name: Recruit
    permissions:
      - USE_HOME
  '9': # Priority level (higher number = higher rank)
    name: Veteran   # Role name
    permissions: # List of permissions
      - USE_HOME
      - ACCESS_BANK
      - ACCESS_ENDERCHEST
  '10':
    name: Captain
    permissions:
      - USE_HOME
      - ACCESS_BANK
      - ACCESS_ENDERCHEST
      - MANAGE_MEMBERS
      - SET_HOME

List of Permissions

Below is a list of available permissions that can be assigned to roles:

  • MANAGE_MEMBERS: Allows adding, removing, promoting, and demoting team members. (You can only promote to the rank below yours and demote people under you)
  • MANAGE_ALLIANCE: Allows managing alliances with other teams.
  • ACCESS_BANK: Allows access to the team bank.
  • ACCESS_ENDERCHEST: Allows access to the team's shared Ender chest.
  • USE_HOME: Allows teleporting to the team home.
  • SET_HOME: Allows setting the team home location.
  • SWITCH_FRIENDLY_FIRE: Allows enabling or disabling friendly fire.

Below is a list of available permissions that can be assigned to roles:

List of Permissions

Team-Roles:
  '-1':  # MANDATORY ROLE
    name: Recruit
    permissions:
      - USE_HOME
  '1':  # # MANDATORY ROLE
    name: Recruit
    permissions:
      - USE_HOME
  '9': # Priority level (higher number = higher rank)
    name: Veteran   # Role name
    permissions: # List of permissions
      - USE_HOME
      - ACCESS_BANK
      - ACCESS_ENDERCHEST
  '10':
    name: Captain
    permissions:
      - USE_HOME
      - ACCESS_BANK
      - ACCESS_ENDERCHEST
      - MANAGE_MEMBERS
      - SET_HOME

Here’s an example of the configuration for it

The -1 represents the owner role and the 1 represents the default role.

The roles with priority 1 and -1 are mandatory; if you remove them, you will break your data. Please do not do that.

⚠️ Reminder ⚠️

Roles are organized by priority, which determines their position in the team hierarchy. A higher priority number indicates a higher rank. For example, a role with priority 10 is higher than a role with priority 2.

How does the role priority work?

A role is basically the rank of the player in your team; it allows your players to have a hierarchy system in their team.

What is a role?

Team Role Settings

  • SWITCH_FRIENDLY_FIRE: Allows enabling or disabling friendly fire.

Leaderboard

In ZelTeams, there are two leaderboards available, the Placeholder based on the for your holograms and such, and a GUI-based one that can be found with the /team leaderboard command.

You can check the Placeholders into the right section of the wiki, and for the GUI, it follows the same guidelines as the others; you can check the GUI section for that.

Score System

Teams are ranked in the leaderboard using a special score system that's based on kills, deaths, and bank balance. Here is the exact explanation:

Score = (Kills × Kill Factor) + (Money × Money Factor) - (Deaths × Death Factor) (Factors are defined in the configuration)

Where:

  • Kill Factor = how much each kill is worth in points
  • Money Factor = how much each unit of money is worth in points
  • Death Factor = how many points are subtracted per death

Example: If Kill Factor = 10, Money Factor = 0.01, Death Factor = 5

Player with 20 kills, $5000, 3 deaths Score = (20 × 10) + (5000 × 0.01) - (3 × 5) = 200 + 50 - 15 = 235 points

The formula rewards kills and money while penalizing deaths, with each factor allowing you to control how much weight each stat has in the final score.


Chat Listener Priority

Different servers use different chat plugins (Although ZelChat is the best on the market), which can sometimes cause conflicts with our team chat and ally chat features.

When this happens, messages may appear in both the team/ally chat AND the main server chat at the same time.

The Problem:

  • Your chat plugin and our plugin are both trying to handle the same chat message, resulting in duplicate messages.

The Solution:

  • We've included chat listener priority settings that let you adjust how our plugin interacts with your existing chat system. By tweaking these settings, you can ensure messages only appear where they're supposed to.

Need Help? These settings are more technical to configure. If you're having chat conflicts or need assistance adjusting the listener priority, please reach out to our Discord for support.


Friendly Fire & Explosions

Friendly fire protection (toggleable per team by roles with the SWITCH_FRIENDLY_FIRE permission) covers direct attacks, projectiles, end crystal explosions, and respawn anchor explosions. Teammates — and allies, when alliances are enabled — cannot be damaged by an anchor or crystal that another team member detonates. Blowing yourself up still works as normal, and WorldGuard forced friendly-fire regions are respected.


Vanish Plugin Support

ZelTeams hooks into AdvancedVanish automatically — no configuration needed. Vanished players are treated as offline: they cannot receive team or ally invites and are hidden from command tab completion, so vanish is never leaked. Staff with AdvancedVanish's vanish-priority permission to see a vanished player still see them normally. Other vanish plugins that expose the standard vanished metadata (SuperVanish, PremiumVanish, EssentialsX) are supported as a fallback.