Redwood derives no gather site: its trees and their bank are two planes apart #136

Open
opened 2026-08-06 13:16:52 +00:00 by sickday · 0 comments
Owner

Redwood is a legal ::botgen target and derives no site anywhere, so a fleet
pointed at it spawns and stands still. The command warns.

Measured against the operator's cache:

loc ids 29668, 29670, 12 placements each
planes 1 and 2
nearest bank on the same plane 873 (plane 1), 198 (plane 2)
nearest bank on any plane 20 — the Woodcutting Guild chest at {0, 1592, 3475}

So the trees and their bank are twenty tiles apart and two storeys apart, and
Bot.Sites.same_plane_bank/2 will not look a plane down.

Relaxing that filter alone would make things worse, not better:
Bot.Travel.hop/2 keeps the bot's own plane and discards the destination's,
and nothing in the bot layer climbs a ladder. A cross-plane pairing would send
a bot walking to the tile below the bank forever, which is a harder failure to
read than a bot that never leaves.

Measure before building anything

Redwood standing on planes 1 and 2 inside a guild that is at ground level is
suspicious on its own. World.Collision's loc index was storing bridge-tile
locs one storey above the tile they are clicked from — 56,800 placements — and
this has exactly that shape. Re-derive the table after that fix lands before
deciding redwood needs cross-plane travel at all.
If the placements come back
on plane 0, the guild chest is 20 tiles away and redwood works with no further
change.

If they do not, this becomes a bot-navigation issue: a leg that crosses planes
needs the transport table (World.Transports) in the route, which is a larger
piece of work than the pairing rule it looks like.

Redwood is a legal `::botgen` target and derives no site anywhere, so a fleet pointed at it spawns and stands still. The command warns. Measured against the operator's cache: | | | |---|---| | loc ids | `29668`, `29670`, 12 placements each | | planes | 1 and 2 | | nearest bank on the same plane | 873 (plane 1), 198 (plane 2) | | nearest bank on any plane | 20 — the Woodcutting Guild chest at `{0, 1592, 3475}` | So the trees and their bank are twenty tiles apart and two storeys apart, and `Bot.Sites.same_plane_bank/2` will not look a plane down. Relaxing that filter alone would make things **worse**, not better: `Bot.Travel.hop/2` keeps the bot's own plane and discards the destination's, and nothing in the bot layer climbs a ladder. A cross-plane pairing would send a bot walking to the tile below the bank forever, which is a harder failure to read than a bot that never leaves. ## Measure before building anything Redwood standing on planes 1 and 2 inside a guild that is at ground level is suspicious on its own. `World.Collision`'s loc index was storing bridge-tile locs one storey above the tile they are clicked from — 56,800 placements — and this has exactly that shape. **Re-derive the table after that fix lands before deciding redwood needs cross-plane travel at all.** If the placements come back on plane 0, the guild chest is 20 tiles away and redwood works with no further change. If they do not, this becomes a bot-navigation issue: a leg that crosses planes needs the transport table (`World.Transports`) in the route, which is a larger piece of work than the pairing rule it looks like.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Revenant/Server#136
No description provided.