The session clock: your battle log every 30 minutes while you play, and a page that says what the recorder lost

The recorder was losing about 4% of all battles - some 7,000 a week - and knew it only as a count of 'gaps'. Measured against the game's own lifetime battle counter, the loss came almost entirely from long sittings that began inside a long wait: the old schedule estimated each player's pace and waited up to a day for the quiet ones, and a battle is three minutes, so a sitting fills the 30-entry log in ninety. The schedule is now one rule: while you are playing, your log is read every 30 minutes; after a read that found nothing the wait doubles, and it never passes two hours. Your profile is read once a day and once after a session. The cost is more reads - about two and a half times as many battle-log calls, most of them empty and bodiless - inside the same budget, and the loss should fall to near zero. Status > Efficiency shows both, per day: reads, how many found nothing, gaps, and battles lost, measured nightly. Recording and coverage carries the new promise.