01
Fight pulse
Ancient health and clan-score bursts share the same elapsed-time axis.
Ancient Summons analytics
Understand every Ancient Summons fight
Review the Ancient’s health, your clan’s scoring pace, and each player’s observed contribution in one report built from the completed capture you choose to upload.
Captures stay in this browser until you explicitly select and upload them.
Ancients event · Eight summons
Obsidian Reach · K118
Clan score
72,910,000
#1
6.4M
05:48
Complete coverage
#2
7.2M
06:31
Complete coverage
#3
7.9M
07:04
Complete coverage
#4
8.6M
07:46
Uncertain coverage
#5
9.3M
08:12
Complete coverage
#6
10.1M
08:57
Complete coverage
#7
11M
09:35
Complete coverage
#8
12.3M
10:18
Complete coverage
Summon 8 · Level 132 · 12,260,000 total health
Fight pulse
Ancient health
100% → 0%
Clan-score intervals
12,260,000
41 players observed
Player contributions
Lyra Vale
Early phase
3.1M
25.6%
Torin Ash
Middle phase
2.5M
20.2%
Sable Reed
Final phase
1.9M
15.7%
Observed intervals are shown without inventing an exact attack second.
What Runekist shows
From one captured fight to a report your clan can use
Runekist keeps health, clan scoring, player contribution, and the surrounding Ancients event together without pretending an observed score interval is an exact attack time.
02
Player contributions
Compare score, share, captured intervals, observed first-score phase, and an expandable pulse for each player.
03
Complete event history
Review every uploaded summon in the same game-reset event with per-fight score and duration.
How collection works
Four deliberate steps from browser to report
Monitoring and capture happen locally first. Upload is a separate choice.
Read the setup guide-
01Install the extension and link a Runekist clan. A Leader or Superior approves the clan-scoped connection. -
02Start monitoring in the Total Battle tab. Capture data is stored in that browser first. -
03Open Events → Rise of the Ancients → Clan Member details once. This initializes validated clan-score sampling for the active fight. -
04Select the completed capture and upload it to Runekist. Only the completed capture you select is sent.
Privacy and control
Local first, explicit upload
Starting monitoring does not upload or publish anything. You decide which completed captures leave your browser.
Capture stays local first
Monitoring stores capture data in the browser you chose.
Upload is always selected
Only selected completed captures are uploaded to Runekist.
The connection is limited
Access is clan-scoped, revocable, and does not receive your normal Runekist browser-session cookie.
Clan leadership approves it
An active Leader or Superior must approve the destination clan.
Frequently asked questions
Before you connect a browser
Who may link the collector to a clan?
A Runekist clan Leader or Superior with an active membership may approve the connection.
Does anything upload automatically?
No. Monitoring stores captures locally. You must select a completed capture and upload it.
Does Runekist receive my Total Battle credentials?
No. The collector does not collect your Total Battle login credentials, cookies, or authorization headers.
Can I use the collector with multiple clans?
Yes. Link or switch the Runekist destination deliberately and verify the clan before uploading.
What happens if I close or reload the game tab?
Keep the selected tab open while monitoring. After a reload, the collector restores the local session and resumes when possible.
Why must I open Clan Member details once?
It provides the validated request the collector needs to sample clan-ranking changes for the active Ancient.
Why can report segments be uncertain or unobserved?
Monitoring can start late or be interrupted. Runekist shows the supported interval instead of inventing an exact attack time or health value.
Can I revoke a linked browser?
Yes. Revoke a linked installation from Runekist account settings or from the extension.
See the result before setup
Explore a synthetic Ancient report
The public demo uses fictional players, identifiers, fights, and scores.