01
Fight pulse
Observed Ancient health and clan-score bursts share the same elapsed-time axis.
Ancient Summons analytics
Review captured clan score, recording coverage, and each player’s observed contribution in one report built from the fights you choose to upload.
Captures stay in this browser until you explicitly select and upload them.
Ancients event · Eight summons
Summon 8 · Level 132 · Captured clan score 12,260,000
41 players observed
What Runekist shows
Runekist keeps observed health, captured clan score, player contribution, and the surrounding Ancients event together without presenting uncertain data as exact.
01
Observed Ancient health and clan-score bursts share the same elapsed-time axis.
02
Compare score, share, captured intervals, observed first-score phase, and an expandable pulse for each player.
03
Review each uploaded summon with its captured clan score, duration, player count, interval count, and recording coverage.
Recording confidence
Each fight says what the recording supports. These labels stay separate from the captured clan score.
How collection works
Monitoring and capture happen locally first. Upload is a separate choice.
Read the setup guide01
02
03
04
05
06
07
08
Privacy and control
Starting monitoring does not upload or publish anything. You decide which completed captures leave your browser.
Monitoring stores capture data in the browser you chose.
Only selected completed captures are uploaded to Runekist.
Access is clan-scoped, revocable, and does not receive your normal Runekist browser-session cookie.
An active Leader or Superior must approve the destination clan.
Frequently asked questions
A Runekist clan Leader or Superior with an active membership may approve the connection.
No. Monitoring stores captures locally. You must select a completed capture and upload it.
No. The collector does not collect your Total Battle login credentials, cookies, or authorization headers.
Yes. Link or switch the Runekist destination deliberately and verify the clan before uploading.
Reopen the intended tab and allow the Unity game to finish loading. The collector reconnects to the current local recording session.
When Rise of the Ancients becomes active, check the collector before the first Ancient is summoned.
Only if the collector shows “Open Ancient once,” open Events → Rise of the Ancients → Clan Member details, then close the panel.
Do not reopen the Events page after recording initializes because it can interrupt ranking capture. Use the extension’s “This account” score to follow your own progress instead.
The game does not always expose its official summon counter. When that happens, the collector may use the order of summons observed in the current recording session and marks that value as inferred when the source is available.
Not necessarily. It is the score supported by captured clan-ranking changes. Runekist shows health separately and only treats health as authoritative when the game supplied that metadata.
Yes. Upload the corrected capture again. Runekist updates the existing fight, marks it as corrected, and keeps the same fight link.
Monitoring can start late or be interrupted. Runekist shows the supported interval instead of inventing an exact attack time or health value.
Yes. Revoke a linked installation from Runekist account settings or from the extension.
See the result before setup
The public demo uses fictional players, identifiers, fights, and scores.