Repository navigation
Regroup 'cmd summon' pauses the run and needs a resume; record the observer's regroup/resume in report.remote #270
Description
Found in the 2026-10-20 full observer runs (ZF #257, RFC #258, Uldaman #261, WC); data in ~/TortoiseBots-audit/tests/full-obs-*-19z16/, lessons entries zf/rfc/uldaman/wc-full-19z16 in RUN-LESSONS.md, analysis ~/TortoiseBots-audit/RFC-DEATHS-ANALYSIS.txt. Module code is Sagiroth/TortoiseBots feat/dungeon-self-clear (ours to merge into); tracked here.
Evidence (RFC run 2b 15:44:1x-15:46:24): the observer's regroup order (3x cmd summon, ACKed) paused the run ('player order (cmd summon): .bot run resume to go on'); the only human-needed pause of that run. Fix: a regroup summon during a run should not pause (or auto-resume once the summon has landed), and the agent should record the observer's regroup and resume in report.remote, not only the chat line. Related: #252 (regroup waits for a bot already at the lead).
Activity
Merge pull request #299 from pjerra/fix-ta270-player-orders
pjerra commentedon Oct 23, 2026
Agent side merged in #299: the observe report lists each pause the run leader makes for a player's order in
report.remote.observe.player_orders(step and order),controlsrecordsplayer order: ...and the resume after it (a pause that ends in a stop records no resume), and aplayer_ordertrace event is written. The agent sends nothing new. Still open: the module side (TortoiseBotsPauseForPlayer): whether acmd summonduring a run should skip the pause or resume by itself is a module decision.pjerra commentedon Oct 26, 2026
Fixed in TortoiseBots fix/ta270-summon (7705da8b):
cmd summon(sends the bot to the lead bot, refused for a bot in combat) no longer pauses the run; every other order, cmd revive included, still pauses. Merged in integ/20d (98ea955a), reviewed by Codex and Opus, deployed as all-fixes-20d2 on both test servers with no regression in the 2026-10-26 proof runs. Closing.