# Instance/navigation first-fix build recovery

- Safe logout requested approximately 2026-11-01 11:26 CET after pausing
  `Clientless.Adventure.Loader` and TestBot admission.
- Build was allowed to run in parallel by the user's explicit clarification;
  installation/restart remained gated by zero bots or the five-minute limit.
- At 11:31 CET, nine managed bots remained after more than five minutes.
  The server was therefore eligible for a clean shutdown under the agreed rule.
- The separately logged-in human `Allitester` (GUID 21) is not a managed bot.

| GUID | Name | faction | saved map/position | observed state before shutdown |
|---:|---|---|---|---|
| 40 | Drakagmok | Horde | 1 / -4009.801 -2003.480 121.296 | groupformation; native taxi chain; no free-flight/transport record |
| 43 | Fizzira | Alliance | 0 / -8830.011 635.672 119.259 | social; failed held free flight, 94 segments |
| 60 | Ashani | Alliance | 1 / 7990.230 1296.750 59.628 | leisure; no flight capability/state |
| 77 | Drakogzug | Horde | 1 / 1852.910 -4570.060 24.981 | economy; flight and local travel arrived |
| 83 | Mahuwa | Horde | 571 / 2906.229 6057.960 80.671 | profession; zeppelin arrived; free flight failed touchdown confirmation |
| 96 | Darden | Alliance | 0 / -9337.900 12.744 105.163 | profession; failed held free flight, 162 segments |
| 121 | Braneven | Horde | 0 / 1964.780 -1567.223 123.819 | rest; failed held free flight, 462 segments |
| 132 | Braneron | Horde | 0 / 2539.960 -53.784 28.107 | no intent/travel/flight/transport state |
| 153 | Ragnli | Alliance | 0 / -11787.057 -3180.120 -29.714 | no intent/travel/flight/transport state |

Aggregate immediately before diagnostics: nine sessions, three combat and six
flight flags. No bot was individually force-logged-out, teleported, detached or
removed to enable the build.

## Restart outcome

- Build `-j10`, installation and fresh startup succeeded.
- Fresh worldserver PID 153100 reached `(worldserver-daemon) ready...`; TCP
  listeners 8085 and 8087 were verified.
- All nine bots were loaded explicitly before restoring the population loader.
- None retained an old free-flight or transport controller record. Normal new
  intent travel/combat resumed, so no recovery teleport was necessary.
- Loader and TestBot admission were restored. Population status reported
  `enabled=1 schema=1 busy=0`, targets `50/5/50/5`; staggered loading resumed.