Scenarios time out at the first map wait because the teleport right after a save loads doesn't take #112
Labels
No labels
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Beanstalk#112
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🤖 Many gameplay cells end with
a step ran out of time: timeout: not met in time. That is the game bridge's reply when awaitforevent = "map"reaches its timeout. The first step of the scenarios involved is ateleportstraight afterstart = "save:kokiri-start", usually toHyruleField_Child, followed by that wait withtimeout_s = 60.What the reports show:
Likely cause (from Longshot's side): the game's teleport (
oot_teleport,host/hos_main.c) refuses or drops a request while an event plays or a map loads. It also takes only one request every 8 s. Just after a save loads, the save's own opening event can still be running. A refused teleport is retried, but one that was accepted while an event was about to start seems to be lost silently, and the wait then runs out.Workaround we're trying on our PRs:
wait_s = 10before the teleport andtimeout_s = 120on the map wait (rounds started 2026-11-20 04:45Z on #1776, #1282, #1574). If those pass, the default plan'shyrule-fieldcould do the same.Asked:
playwith no event playing before the first teleport.cheats: teleport …log lines in the report, so the cause shows without the full log.Possibly related, for context: