Improve AdventureBot instance and flight navigation
This commit is contained in:
1 parent
be049baacc
commit
3c361e435a
14 files changed
+525
-63
No files matched your search
@@ -0,0 +1,50 @@
|
||||
# Adventure portal unlock build recovery
|
||||
|
||||
Safe logout was requested while the `-j10` build started in parallel. The build
|
||||
completed successfully. At the five-real-minute installation boundary eleven
|
||||
managed sessions remained (`combat=4`, `transport=0`, `flight/taxi=7`). `saveall`
|
||||
completed before shutdown.
|
||||
|
||||
| GUID | Name | Faction | Saved position | Observed transition/action |
|
||||
|---:|---|---|---|---|
|
||||
| 26 | Arthoran | Alliance | map0 `-11080.00,-483.45,54.49` | failed bounded free flight; mounted hold |
|
||||
| 60 | Ashani | Alliance | map530 `-3013.51,-13204.10,59.63` | native taxi 94 -> 27 |
|
||||
| 77 | Drakogzug | Horde | map1 `1852.91,-4570.06,24.98` | no flight/transport; failed departure recovery |
|
||||
| 80 | Noralin | Alliance | map530 `-3013.51,-13204.10,59.63` | native taxi 94 -> 27 |
|
||||
| 90 | Dorndin | Alliance | map1 `7990.23,1296.75,59.63` | native taxi 27 -> 94 |
|
||||
| 93 | Gargar | Horde | map571 `2277.05,5202.07,12.49` | flight arrived; zeppelin state arrived |
|
||||
| 96 | Darden | Alliance | map0 `-9381.78,-59.96,93.02` | failed bounded free flight; mounted hold |
|
||||
| 97 | Talzul | Horde | map1 `2035.92,-3467.29,171.71` | failed bounded free flight; mounted hold |
|
||||
| 132 | Braneron | Horde | map0 `2602.82,-112.11,34.02` | idle; no flight/transport |
|
||||
| 135 | Ragnhild | Alliance | map1 `7990.23,1296.75,59.63` | native taxi 27 -> 94 |
|
||||
| 153 | Ragnli | Alliance | map0 `-11787.06,-3180.12,-29.71` | idle; no flight/transport |
|
||||
|
||||
Loader configuration and test admission remained disabled/paused through the
|
||||
build, installation and restart window. Post-start recovery outcomes are added
|
||||
below after verification.
|
||||
|
||||
## Post-start verification
|
||||
|
||||
- Fresh worldserver PID 174775 reached ready state; TCP 8085 and 8087 listen.
|
||||
- All eleven recorded characters were loaded. Every prior free-flight, native
|
||||
taxi and transport state was absent after login; ordinary schedules then
|
||||
produced new behavior independently of the saved transition state.
|
||||
- Targeted production-method tests exercise both paths: native GameObject use
|
||||
when prerequisites pass, and the importer-validated fixed teleport when a
|
||||
level-80+ AdventureBot lacks quest prerequisites. Arrival still requires a
|
||||
changed clientless teleport sequence, correct map and <=5-yard target error.
|
||||
- A level-85 Elanora live probe planned and traversed graph-bound capital portal
|
||||
travel. The explicit Twilight Highlands acceptance and its actual native
|
||||
condition state are documented below.
|
||||
|
||||
## Explicit Twilight Highlands acceptance
|
||||
|
||||
Elanora (level 85) was placed within native interaction range of Stormwind spawn
|
||||
200627 and given only target `portal_go_200627_target`. Production navigation
|
||||
log at 2026-11-01 16:57:17 records edge 1801 `portal_use`, spawn 200627, spell
|
||||
85545, followed in the same second by `EDGE_COMPLETE` on map 0 with
|
||||
`arrivalError=0.00`. Runtime area query at the destination resolved area 5140,
|
||||
allowed, level band 84-85. The World DB has no spell-condition rows for 85545,
|
||||
so this particular portal correctly used the unchanged native click path rather
|
||||
than `PORTAL_ADVENTURE_UNLOCK`. The questless unlock path remains covered by the
|
||||
production-method regression. Temporary Elanora profile and override removed.
|
||||
@@ -0,0 +1,103 @@
|
||||
# Generic flight-entry build recovery
|
||||
|
||||
- Safe logout requested at approximately 2026-11-01 12:02 CET after pausing
|
||||
`Clientless.Adventure.Loader` and TestBot admission.
|
||||
- The `-j10` build ran in parallel with the safe drain, per the corrected build
|
||||
policy in `AGENTS.md`, and completed successfully.
|
||||
- At 12:08 CET, more than five real minutes later, 13 managed sessions remained:
|
||||
3 combat flags, 0 active transports and 9 native flight flags. The database
|
||||
positions below are from the immediately preceding online snapshot; native
|
||||
action/flight/transport diagnostics were also captured in the tmux console.
|
||||
|
||||
| GUID | Name | faction | saved map / position | observed state |
|
||||
|---:|---|---|---|---|
|
||||
| 40 | Drakagmok | Horde | 1 / -4777.22 -1264.89 15.78 | native taxi 22->42; no free-flight/transport record |
|
||||
| 48 | Elaniel | Horde | 1 / -4647.84 -1609.87 23.93 | native taxi 22->42; no free-flight/transport record |
|
||||
| 54 | Falaeriel | Horde | 0 / 1875.88 -5018.08 166.81 | native taxi chain; prior free flight arrived |
|
||||
| 77 | Drakogzug | Horde | 1 / 1857.05 -4568.03 24.98 | travel completed; no active flight/transport |
|
||||
| 80 | Noralin | Alliance | 1 / 7990.23 1296.75 59.63 | native taxi; old ship record already Arrived |
|
||||
| 83 | Mahuwa | Horde | 571 / 4234.13 3346.45 391.19 | failed free flight/permission timeout |
|
||||
| 87 | Moggra | Horde | 1 / -3230.20 -1945.24 156.47 | native taxi to node55 |
|
||||
| 91 | Norara | Horde | 571 / 3588.17 6692.83 208.30 | failed bounded flight corridor |
|
||||
| 104 | Lillini | Alliance | 1 / 2669.46 1667.13 393.02 | native taxi; old flight/ship records Arrived |
|
||||
| 118 | Lillina | Alliance | 0 / -8768.04 583.35 133.27 | failed bounded flight corridor |
|
||||
| 132 | Braneron | Horde | 0 / 2539.96 -53.78 28.11 | idle; no flight/transport state |
|
||||
| 146 | Loraria | Horde | 1 / -4215.50 -1913.36 131.73 | native taxi 22->42 |
|
||||
| 153 | Ragnli | Alliance | 0 / -11787.10 -3180.12 -29.71 | idle; no flight/transport state |
|
||||
|
||||
No bot was individually force-logged-out, teleported, detached, or removed to
|
||||
enable the build. Installation/restart uses the documented five-minute clean
|
||||
shutdown exception. Post-start recovery results must be appended below.
|
||||
|
||||
## Restart outcome
|
||||
|
||||
Pending.
|
||||
|
||||
## Second build drain
|
||||
|
||||
- A second safe drain was requested at approximately 12:15 CET for the
|
||||
flight-budget correction. The incremental `-j10` build again ran in parallel
|
||||
and succeeded.
|
||||
- After the five-minute gate, only two sessions remained online; neither had an
|
||||
active free-flight or transport record:
|
||||
|
||||
| GUID | Name | faction | saved map / position | observed state |
|
||||
|---:|---|---|---|---|
|
||||
| 77 | Drakogzug | Horde | 1 / 1852.91 -4570.06 24.98 | completed location travel; outdoors=0 |
|
||||
| 153 | Ragnli | Alliance | 0 / -11787.10 -3180.12 -29.71 | idle; no flight/transport state |
|
||||
|
||||
The other three members of the earlier five-bot snapshot logged out safely
|
||||
before this final snapshot. No individual force logout was used.
|
||||
|
||||
## Third build drain
|
||||
|
||||
- Final macro-connector prioritization build started in parallel with a safe
|
||||
drain at approximately 15:47 CET and completed successfully with `-j10`.
|
||||
- At the 15:52 CET installation gate, GUID 77 Drakogzug and GUID 153 Ragnli
|
||||
remained in combat at the same positions recorded above. Both had zero active
|
||||
free-flight and transport records. They were not interrupted or individually
|
||||
logged out; the documented clean-shutdown exception was used.
|
||||
## Fourth build drain (portal-continuation budget fix)
|
||||
|
||||
- Safe logout requested at approximately 2026-11-01 15:54:30 CET. The `-j10`
|
||||
build started immediately in parallel and completed successfully.
|
||||
- At the five-minute installation boundary, two clientless sessions remained;
|
||||
neither was in free flight, taxi travel or on a transport:
|
||||
- GUID 77, Drakogzug, Horde, map 1 at `(1852.91, -4570.06, 24.98)`, area
|
||||
1637. Action had failed at `flight_departure`; no free-flight or transport
|
||||
state was present.
|
||||
- GUID 153, Ragnli, Alliance, map 0 at `(-11787.06, -3180.12, -29.71)`, area
|
||||
72. Action executor was idle; no free-flight or transport state was present.
|
||||
- GUID 168 Elanora completed her active movement state and logged out safely
|
||||
before the boundary. The temporary route-test Lua override was removed from
|
||||
the source tree before this build.
|
||||
- Testbot admission remained paused. AdventureBot loader remained disabled in
|
||||
runtime configuration throughout the build and restart window.
|
||||
|
||||
## Fifth build drain (destination-first probe fix)
|
||||
|
||||
- Safe logout requested at approximately 2026-11-01 16:04:15 CET. Build
|
||||
`-j10` again ran immediately in parallel and succeeded.
|
||||
- GUID 168 Elanora completed her active free-flight transition and logged out
|
||||
safely. At the five-minute installation boundary GUID 77 Drakogzug and GUID
|
||||
153 Ragnli remained online in the same saved positions recorded above.
|
||||
- `saveall` completed before shutdown. Both remaining bots again reported no
|
||||
free-flight or transport state. Drakogzug had a failed travel action at
|
||||
`flight_departure`; Ragnli was idle. Test admission and the AdventureBot
|
||||
loader remained paused/disabled.
|
||||
|
||||
## Final runtime result
|
||||
|
||||
- Fresh worldserver PID 172446 reached `(worldserver-daemon) ready`; TCP 8085
|
||||
and 8087 are listening.
|
||||
- GUIDs 77 and 153 were loaded after restart. Both had no stale free-flight or
|
||||
transport state and resumed ordinary behavior.
|
||||
- The controlled Elanora plan produced a valid direct free-flight route from a
|
||||
regular graph node to `portal_at_6354_source`; no MMAP attachment was needed.
|
||||
The Stormwind Twilight Highlands portal did not compete because edge 1801
|
||||
correctly failed `PortalPrerequisites` for this character's native spell/
|
||||
quest state. The relevant portal is otherwise the first geometric connector,
|
||||
so this was not a probe-budget failure.
|
||||
- Temporary Elanora override removed. Schedule restored. Loader configuration
|
||||
restored to enabled and test admission resumed. Loader status confirmed
|
||||
`enabled=1 schema=1 busy=0`, pools `50/5/50/5`.
|
||||
@@ -0,0 +1,36 @@
|
||||
# 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.
|
||||
Reference in new issue
Block a user