Skip to content

Assigning scoreboards ​

A board is only shown to a player when FeatherBoard considers it assigned to that player. Assignment can be based on permissions, Vault groups, worlds, time, client language, distance to spawn or a PlaceholderAPI value.

How selection works ​

  1. FeatherBoard asks each loaded board whether it matches the player.
  2. Matching boards are sorted by priority (highest first).
  3. The first board in that order is shown.

A board matches if any of the configured assigning methods matches. The methods are combined with OR, not "first method wins". If you want a board to match only one method, give it its own assigning setting.

yaml
# config.yml
assigning:
- 'PERMISSION'
yaml
# scoreboards/vip.yml
settings:
  priority: 20
  # Only use the permission check for this board.
  assigning: 'PERMISSION'

Use priorities, not ordering

Your YAML files are loaded in filesystem order. Always set priority when two boards could match the same player. Higher numbers win.

Permission assignment (default) ​

The default method checks featherboard.group.<boardname>.

text
/lp group default permission set featherboard.group.default true
/lp group vip permission set featherboard.group.vip true

Every board except default is registered with a default of false, so grant the permission explicitly. featherboard.group.default is true by default, which is why the sample board works out of the box.

Use PERMISSION_CACHED if your permission plugin queries a database on every check. It caches the result until the player relogs or toggles the scoreboard.

yaml
assigning:
- 'PERMISSION_CACHED'

Vault groups ​

GROUP compares the player's primary Vault group with the board name. Vault and a permissions plugin are required.

yaml
assigning:
- 'GROUP'

With this setting, a board called vip.yml is shown to players whose primary group is vip. Board names must match group names exactly (case-insensitive).

Worlds ​

WORLD matches the board name against the world name.

yaml
assigning:
- 'WORLD'

Create world.yml, world_nether.yml and world_the_end.yml for a multi-world setup. You can combine world assignment with permissions:

yaml
assigning:
- 'WORLD'
- 'PERMISSION'

Because methods are OR'ed, a board is shown when either condition matches. If you need "world AND permission", use a PLACEHOLDER condition or a board script instead.

Time of day ​

TIME uses the board names day and night:

yaml
assigning:
- 'TIME'

Daytime is roughly 06:00–18:00 in Minecraft time. Players switch boards when the world time crosses the boundary.

Client language ​

LANGUAGE uses the player's client locale. Create boards named en.yml, nl.yml, fr.yml, and so on.

yaml
assigning:
- 'LANGUAGE'

If no board matches the player's language, no board is assigned by this method. Combine it with PERMISSION for a fallback.

Placeholder value ​

PLACEHOLDER:<placeholder> assigns a board when the resolved PlaceholderAPI value equals the board name. Use the %...% syntax, not {...}.

yaml
assigning:
- 'PLACEHOLDER:%player_world_environment%'

You can also prefix board names with placeholder_:

yaml
# board file: placeholder_survival.yml
assigning:
- 'PLACEHOLDER:%server_type%'

This is powerful but can be expensive if the placeholder queries a database on every update. Prefer PERMISSION_CACHED or a very stable placeholder.

Distance to spawn ​

SPAWN_DISTANCE selects boards named spawn_distance_<blocks>:

yaml
assigning:
- 'SPAWN_DISTANCE'
text
scoreboards/
├── spawn_distance_10.yml    # within 10 blocks of spawn
├── spawn_distance_50.yml    # within 50 blocks
└── spawn_distance_200.yml   # within 200 blocks

All three boards match a player standing at spawn. Set priorities so the closest board wins:

yaml
# spawn_distance_10.yml
settings:
  priority: 30

# spawn_distance_50.yml
settings:
  priority: 20

# spawn_distance_200.yml
settings:
  priority: 10

Manual assignment ​

NONE disables automatic assignment. Show boards explicitly with /fb show:

yaml
assigning:
- 'NONE'
text
/fb show myboard
/fb hide myboard

A manual show adds an override that survives relogs until the player is shown another board or the override is cleared. Use this for arenas, lobbies and scripted events.

Disabling boards ​

  • Remove featherboard.group.<board> from a player, or negate it in your permissions plugin.
  • Add the world to disabled-worlds in config.yml.
  • Set enabled: false in the board's settings.
  • Use /fb off to hide the scoreboard for a player.

The FAQ has more troubleshooting for boards that do not appear: the board does not appear.

Complete example ​

yaml
# config.yml
assigning:
- 'PERMISSION'
disabled-worlds:
- 'creative'

# scoreboards/spawn.yml
settings:
  priority: 30
  assigning: 'PERMISSION'
  fallback: 'default'

title:
  frames:
    - '&6&lSpawn'
  interval: 20

lines:
  welcome:
    frames:
      - '&7Welcome, &f%player_name%'
    interval: 20
  online:
    frames:
      - '&7Online: &a%server_online%'
    interval: 20

Grant featherboard.group.spawn to the players who should see it, and put a priority of 30 on it so it wins over a lower-priority general board.

Released under a proprietary license. FeatherBoard is not affiliated with Mojang or Microsoft.