Assignment Criteria

Assignment Criteria

Criteria in KiteBoard are used to dynamically allocate different groups to different players based on number of rules. Criteria may be combined or nested to build powerful logic.

Skip to:

• Priority
• World-based criteria
• Permission-based criteria
• Event triggers
• Advanced criteria
• Troubleshooting

Priority

All groups in KiteBoard support a hierarchical priority system, this means scoreboards with a a higher priority will be assigned over lower ones.

You can define a scoreboard priority in the settings block:

setting:
  priority: 1

KiteBoard 3 introduced support to combine multiple assignment methods, this mean you can use any of the below in combination with each other.

World-based criteria

Assign a scoreboard when the player is in this world

criteria:
  1:
    type: WORLD
    world: "world_the_end"

Permission based criteria

Assign a scoreboard when the player has a certain permission (or if default: true this is automatically assigned)

criteria:
  1:
    type: PERMISSION
    permission: "your.custom.permission"
    default: true

Event triggers

Assign a scoreboard when the player is involved in a specified event. For more information see Event Triggers

criteria:
  1:
    type: EVENT
    event: org.bukkit.event.player.PlayerJoinEvent
    event-player: getPlayer

Advanced criteria

KiteBoard allows group's to use more than a single criteria. This allows more powerful criteria objectives.

Example 1: Player is in specific world AND has specified permission

criteria:
  operator: AND
  1:
    type: WORLD
    world: "world_nether"
  2:
    type: PERMISSION
    permission: "server.admin"

Example 2: Player has permission "moderator", "admin", or "staff"

criteria:
  1:
    type: PERMISSION
    permission: "moderator"
  2:
    type: PERMISSION
    permission: "admin"
  3:
    type: PERMISSION
    permission: "staff"

Example 3: Player has permission and is in world, or world_nether

criteria:
  operator: AND
  1:
    type: PERMISSION
    permission: "allow-all-players"
    default: true #Given to all players by default
  2:
    operator: OR
    1:
      type: WORLD
      world: "world"
    2:
      type: WORLD
      world: "world_nether"

Checking criteria status

You can check the criteria status by executing

/kiteboard group <groupname>

If your group is a tablist, you will need to specify:

/kiteboard group <groupname> tablist

This will show the loaded criteria, if it appears green, it is current fulfilled by the player executing the command, grey means it is not fulfilled, this feature is available as of 3.1, May 2020:

The image shows we have the correct permissions, and are in world "world" It also shows that we are not in "world_nether" as this is not highlighted green