TribeScore

Configuration

Leaderboard, popup and scoring options for TribeScore.

Configuration is read once when the plugin loads. Every change below needs a server restart to take effect.

Leaderboard

Key	What it does
`PostLeaderboard`	Whether this map may post. Safe to enable on every map — you will still get one board per interval.
`Style`	`Fields`, `Table` or `Ansi`.
`IntervalMinutes`	How often the board posts. Must match across every map in the cluster.

Popups

Key	What it does
`PointPopups.ShareWithTribe`	Sends the popup to every online tribe member rather than only the killer. Each member still honours their own `/score` setting.
`PointPopups.ShareRadius`	Skips tribemates too far away to see the text. `0` means unlimited.
`DisplayScale`	Popup text size.

Scoring

Key	What it does
`Scoring.ScoreCollapsedStructures`	Credits structures that fall as a result of a destroyed load-bearing piece.
`Scoring.CustomStructureOverrides`	Your own per-structure point values. Parsed first, so these always beat the built-in list.

Enabling collapse scoring changes your economy

Without it, only directly damaged structures score — a large raid can count a small fraction of what actually fell. Turning it on can multiply raid totals several times over. Point values tuned under the old behaviour are worth revisiting afterwards.

Structure point values

Structures are priced by matching their class name against an ordered list. The first match wins and values never stack. Your custom list is checked before the built-in one.

Order matters: material entries sit below turret entries, because some turret class names contain a material word. A material word prices anything containing it, not only building pieces.

Match	Default points
Tek turret	75
Heavy turret	50
Generic turret	25
Tek	15
Metal	8
Stone	4
Wood	2
Thatch	1

These values are a starting point

The defaults are a placeholder economy, not a balanced one. Tune them to your server before treating the board as competitive.

Excluding a structure

An override with both its destroy and loss values set to 0 means the class never scores at all: no points, no audit entry, no popup. This is the way to stop incidental objects — loot bags, spent charges — from moving the board.

Finding a structure's real class name

Class names do not always match what you would guess from the game. The plugin logs each distinct structure class once per server lifetime, so the reliable approach is to destroy one of the structures you want to price, read the class name out of the log, and use that in your override.

ClusterSync integration

If you also run ClusterSync, TribeScore can read tribe names from it so a tribe that renamed still shows its current name on the board, and so tribes with no presence on the map where a fight happened still resolve correctly.

It is optional. If ClusterSync is not present, TribeScore carries on with its own stored names.