Configuration

Configuration is read once when the plugin loads. Every change below needs a server restart to take effect. Defaults are the values in the shipped config.json.

General

Database

Point values

Gains and losses are separate settings on purpose, so you can run an uneven economy — for example, losses worth half a kill, so a tribe that is raided once is not buried for good.

Scoring rules

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.

Scoring.StructureOverrides holds the built-in list above; Scoring.CustomStructureOverrides is yours. Each entry takes a Match and a Destroy and Loss value:

"CustomStructureOverrides": [
    { "Match": "Vault",        "Destroy": 40,  "Loss": 40  },
    { "Match": "TekGenerator", "Destroy": 100, "Loss": 100 }
]

• Match is part of the structure's class name, not case-sensitive. List alternatives separated by commas, such as "TekTurret,TurretTek", when you are not sure which way round a name runs.
• Leave out Destroy or Loss and that side uses the generic structure value, so you can reward cracking a vault without changing what losing one costs.
• Within one list the first match still wins, so put the most specific entries first.

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. The shipped custom list already excludes death loot bags and C4 charges.

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.

Tribe identity across maps

ARK does not keep a tribe's ID the same from one map to the next, so without help one tribe's points would be split across several entries that never add up. Scoring.TribeIdentity decides how TribeScore recognises a tribe instead:

When a tribe is recognised by founder and name:

• Two different tribes that happen to share a name stay separate, because their founders differ.
• The same tribe founded on another map by a different member, or under a different name, also counts as a separate tribe.
• Renaming a tribe starts a fresh score from that point on. Renaming it back picks the original score up again.
• A single map, or a brand-new cluster, behaves exactly as it would with tribe IDs until a second map comes into play.

ClusterSync integration

If you also run ClusterSync, TribeScore finds its tribe table on its own — there is nothing else to configure. A tribe that renamed shows its current name on the board, and tribes with no presence on the map where a fight happened still resolve correctly. Any table that maps a tribe ID to a tribe name works, not only ClusterSync's.

• The table must be on the same MySQL server as TribeScore's own database.
• TribeScore only reads from it and never writes there.
• If nothing is found, TribeScore carries on with its own stored names. That is a supported setup, not an error, and a tribe table that appears later is picked up without a restart.

Event creatures

With CustomDinoEvents installed, tribes can earn points for killing or taming its event creatures. Off by default.

"CustomDinoEvents": {
    "Enabled": true,
    "EventDinoKill": 15,
    "EventDinoTame": 40,
    "ProfilePoints": {
        "Apex": { "Kill": 30, "Tame": 75 },
        "Ascended": { "Kill": 15, "Tame": 40 }
    }
}

• These are the only points that come from something other than PvP. A wild event creature has no owner, so the tribe that kills or tames it gains and nobody loses. Leave the feature off if that is not how your server plays.
• Profile names are the ones set in CustomDinoEvents, not case-sensitive. If you add your own profile there, add it here too or it earns the flat values.
• Ignored tribes cannot earn these either.
• CustomDinoEvents must have Integration.PublishEventApi on, which is its default. Once the map is running, the TribeScore log says whether the two plugins found each other.
• If you install CustomDinoEvents after TribeScore has started, restart TribeScore.

Point popups

Every message a player sees is in this block. Set any of them to "" to hide it.

Leaderboard