Clan syncing

Where the data comes from

Clan_Bot reads your clan's member list from the RuneScape clan hiscores. That list holds each member's name, clan rank, clan XP and kills, and nothing else. Skills and the Adventure Log come from each player's RuneMetrics profile instead, on their own schedule (see Player data updates).

How often

Active clans are synced one at a time, in turn, the one updated longest ago first. A clan is never synced again within 5 minutes of its last sync. In practice a clan is refreshed every few minutes; with many clans in the rotation it can take a little longer.

What a sync records

• New names on the list are recorded as joins.
• Names missing from the list are recorded as leaves.
• Rank changes are recorded as promotions or demotions, with the date, which drives "days at current rank".
• Clan XP and kills are updated for everyone. A member whose clan XP went up is marked as active now, which keeps Last active current even for players with a private RuneMetrics profile.
• Citadel: if the weekly reset time has passed, the new citadel week starts, and new citadel visits and caps from members' Adventure Logs are recorded.

Each of these can be posted to Discord through a webhook. If more than 10 of one kind happen in a single sync, they are sent as one summary message instead of one message each.

The first sync

When a clan is first added, everyone on the list is imported. These are not recorded as joins and no join messages are sent. Each member's joined date starts as the day of that import; managers can correct it in the member details on the website.

Name changes

The hiscores don't say when someone changes their name: it looks like one member left and a new one joined in the same sync. When that happens, Clan_Bot compares the two and scores how likely they are the same account:

• clan XP equal or only slightly higher (it can never go down),
• the same clan rank,
• total XP equal or only slightly higher, from RuneMetrics, and
• their top three skills matching.

At 95% or more the name change is applied automatically: the member keeps their history, points, notes, linked account and access, under the new name. Below that it is recorded as a leave and a join. If RuneMetrics is down at that moment, the whole sync for that clan waits and tries again, rather than risk recording a name change as a leave.

Protection against bad data

The RuneScape hiscores sometimes answer with partial or empty data. Clan_Bot guards against acting on it:

• Mass leaves are held. If at least a quarter of the clan (and at least 5 members) disappears in one sync, nothing is changed and the change is held. Only if they are still missing an hour later is it applied, and even then no "member left" messages are sent for them.
• Outages pause syncing. Timeouts and server errors don't count against a clan. When several clans fail in a row, RuneScape is treated as down and syncing backs off until it recovers.
• A clan is only treated as gone after at least 5 failed fetches over at least 24 hours, and only when the clan hiscores confirm the clan no longer exists. It is then deactivated. This usually means the clan was renamed or disbanded.