Nico
54d77d1e4d
Add preparation outings and equipment checks with a five-minute return to the meeting point. Correct static portal visitor casting and level conditions, with native interaction diagnostics. Recover suspended flying mounts, walk to verified takeoff sites, and validate landing and return volumes. Include SQL migrations, targeted regression tests and live validation checkpoints.
2.5 KiB
Group preparation and gathering
During groupformation, bots may independently check equipment, talk and take validated foot outings into surrounding capital streets. Bot group members do not follow their leader continuously during preparation; the leader's shared meeting location and next destination still govern the group. Normal group following resumes outside formation. Only profession_tools is permitted as a profession scene in this intent; gathering/crafting/trainer work remains limited to the profession intent.
The group_search_walk catalog action now lasts120-240s (world migration 2026_10_29_02). Outings select70/110m radii, require a complete native MMAP corridor of at most220m, an outdoor endpoint in the same capital, and retrace the walked route to the meeting. These are surrounding-street searches, not unrestricted tours through the entire city. No route/collision checks are waived.
The last300 seconds before the actual groupformation deadline are a gathering window. At301s remaining preparation is allowed; at300s no new micro action may start (including explicit admin micro commands). The same guard applies to leisure availability and the main action picker. A foot outing finishes its current short checkpoint and retraces visited checkpoints. Other micro scenes end and the bot returns with local pathfinding to its arrival anchor at the shared meeting location. Within3.5m it waits; it does not start another action. A blocked return retries every10s, without a teleport or delaying the next intent. Chat and group invitations remain available.
Normal travel to the meeting, combat/transport safety and an already pending intent change take precedence. The gathering window ends at the deadline: the ordinary schedule/manual transition may then start from the actual position. No requirement for a complete group or every member's presence was added.
The cutoff derives from the existing intent deadline. It therefore also applies after restart, to explicit preparation durations, and to merged multi-hour blocks using their actual end rather than every intervening hour. Gathering bookkeeping is transient; no new persistent schema or profile setting is required.
Native navigation events GROUP_GATHER_START and GROUP_GATHER_READY identify the cutoff and arrival. Adventure status reports waiting/returning/path-retry detail. Tests cover exact cutoff boundaries, preparation cancellation, safe return requests, blocked-path retries, meeting hold and release at the deadline.