Player data updates

What is fetched

For every player, Clan_Bot reads the RuneScape Adventurer's Log API: XP and level in every skill, total XP, and the latest entries of their Adventure Log. Nobody has to make anything public: every member is tracked. Skill changes feed the clan's XP tracking, and Adventure Log entries are what detect citadel visits and caps and award Adventure Log points.

Only players who are an active member of an active clan are fetched. When someone leaves every clan that uses Clan_Bot, their updates stop; when they join one, they are due straight away.

How often a player is fetched

Each player has their own schedule. After every fetch, Clan_Bot looks at when that player was last active and picks the next fetch time from this table. Active players are checked often; players who haven't done anything in a while are checked rarely, which leaves room for everyone else.

"Activity" is the most recent of:

• the last fetch where the player's total XP had gone up (a fetch that finds new XP counts as active right now),
• the last clan sync where their clan XP had gone up (clan XP only rises when they gain XP in a skill), and
• the date of the newest entry in their Adventure Log.

The same date is shown as Last active on the Members page and is what promotion rules use for inactivity. This table applies to everyone except maxed players, who have their own schedule, below.

A player who logs in and trains is back on the 2 hour schedule from their next fetch. Nothing has to be reset by hand.

Maxed players

A player with 200 million XP in every skill can't gain XP, so XP can't show that they are active. Maxed players are always fetched every 2 hours, so their Adventure Log (and citadel caps) are still picked up quickly.

When a fetch fails

• Player not found or an error for that player: they are rescheduled from what is already known about them, using the same table.
• The RuneScape API is down: nothing is written. Affected players are tried again after about 15 minutes, and if most requests fail, Clan_Bot pauses and backs off until the API answers again. No data is lost, it just arrives late.

Order and pace

Players whose fetch time has passed are fetched in small batches, the most overdue first. Requests are spaced out to stay well within what Jagex asks for (under 20 requests per second for everything Clan_Bot sends), so when many players are due at once (for example after an outage or when a large clan joins), some updates can arrive later than the table says.