Headless bot-fleet automation tooling — interested in this upstream, or fork-only? #90
Closed
paleophyte
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I've been building out a headless automation layer on top of wowee, simply called "wowee_headless" — a Python fleet manager (tools/bot_fleet_manager/) that drives one or more logged-in characters via HTTP APIs: movement, pathfinding through a navmesh service, chat/party commands, and a "travel node" graph for chaining city navigation with transports (trams, boats, portals, flight masters).
Most recently it can now do a fully automated round trip through the Deeprun Tram — walk to the entrance, board a moving tram car, ride, disembark, walk to a flight master — in both directions, no manual steps. This was the most recent work developed for a "Grand Expedition" style long-range route planner (Goldshire → Stormwind → Deeprun Tram → Ironforge → … → Darnassus), which is still in progress.
It's all been driven by a fairly detailed plan doc (BOT_PLAN.md) if you want a somewhat more detailed picture of where it's headed.
This is still actively evolving and I consider it experimental — but I wanted to ask: is this something you'd want upstream eventually (maybe once it's more baked), or would you rather this stay a fork-specific extension? No pressure either way, just want to build in the direction that's actually useful to you.
All reactions