Files
Viano-Core/doc/clientless/checkpoints/2026-11-03-elevator-exit
Nico 3aa780662e Complete AdventureBot navigation, instance travel and shutdown fixes
Finish capital waiting travel and adaptive flight entry up to 10,000 yards.
Preserve checked vertical climbs, recover blocked ground departures and find
validated dry landings. Retain group routes and Undercity arrival constraints.

Restore defense from native combat references, coordinate instance rendezvous
and browser reentry, finalize clientless sessions before map destruction and
transfer Halaa capture-point ownership safely.

Include the associated regression tests, investigation reports and reusable
diagnostic scripts. Keep generated runtime evidence and server binaries local
through scoped ignore rules. Validation/build/live evidence is recorded in the
session checkpoint and individual reports.
2026-11-05 10:35:34 +01:00
..

Elevator boarding, exit and five-minute recovery

Final source: ClientlessTransportMgr.h/.cpp and ClientlessTransportDeckMgr.cpp. Type11 boarding begins only at a matching stopped dock with >=500ms remaining; exiting requires stopped dock but no remaining-time budget. Ship, zeppelin and tram budget checks unchanged. An elevator that departs during a transition keeps its passenger and retries without accidentally cancelling the journey. Once on land, final exit movement can finish after the platform departs.

After300000ms as an actual elevator passenger, native TeleportTo moves to the original recorded destination node. Aborted attempts cannot replace that target. Native ACK completes before arrival is published. Unknown, incompatible or forbidden targets do not trigger rescue. Dead characters retain normal death handling. A restored passenger without original boarding history uses the nearest recorded floor and its unique opposite as recovery direction; direction is not persisted across restarts. Source guards and documentation make this explicit.

Validation: test_transport.py (test-transport-3.log) PASS; actual production methods exercised with deterministic world doubles:499/500ms boundary, stopped vs moving/wrong dock, both directions, exactly300000ms, no rescue when on land or riding ships, unchanged destination after cancellation, teleport rejection, short-stop interrupted boarding and final land exit. test_transport_deck_return.py and test_transport_grid_loading.py PASS. Build3-j10 and final install PASS.

Dedicated registered testbot Morvath150, no Adventure profile, used in live run 'elevator-final-20261103'. Both physical and native Arrived states confirmed: 01:14:52 upper node,01:16:16 lower node. Boarding diagnostics show500ms. On downward exit, departure interrupted disembarking; passenger retained and next stop completed successfully (no cancelled result). Test passed in128192ms; no five-minute rescue used. Final testbot automatically logged out. Five-minute rescue was tested deterministically, not by intentionally stranding a live bot. First live run succeeded physically but exposed cancelled outcomes; final source fixes that case and was rebuilt/reinstalled before the final live run.

Build safety: first safe drain00:55:25;10remaining after>5min documented before shutdown. Native shutdown again hit preexisting OPvPCapturePoint NULLcall; core 003512 kept, matching old binary worldserver.crashed in previous checkpoint. First build installed, tested, then continuous second safe drain from01:06:36; 8remaining after311sec documented in shutdown-exception-2.json. No individual forced logout/transport detach to compile. Shutdown core010220 kept, its matching first-fix binary worldserver-first-elevator preserved here. Final process15926 under passiveGDB15915, ready+ports8085/8087+unlimitedcore verified. Crash base worldserver-20261103-011325. Additional model-release debugger breakpoint absent. Loader0 throughout builds/install/restart; restored1 after startup/recovery, original50/5/50/5 pools loading normally. Recovery probes/actions in final startup log: eight recorded bots relogged; taxi48/52 progressing,72 reached node,81 moved from tower to ground;43/61/88/94 native states preserved. Earlier35/121 were natively recovered to faction capitals with post-teleport probes verifying result. No character deletion, dayplan/profile replacement, commit or push.

Final state

110 AdventureBots confirmed online, pools50/5/50/5, pending0, loaderenabled1, error empty. Dedicated test150 is logged out. Mokrak117 naturally used the other Orgrimmar elevator219022 and reached lower node normally at01:19:05, with native Arrived and no forced administrative test/teleport. See mokrak-natural-trip.log. Crash capture remains active under passive GDB. No lag/crash fix claimed.