- The framework — the shared
volvoxtable: a module system, per-character JSON config store, in-game settings UI (built on the bundled StdUi toolkit), minimap button, event/combat-log dispatcher, and logging. - The LootRoute bot — the flagship plugin built on the framework: route following, node scanning, combat handling, flight and skyriding, and quality-of-life tasks such as mailing and repairs.
How it works
WGG loads each Lua file listed inloadorder.json at the repository root, in order, invoking every file with two varargs:
WGG— the unlocker API: object scanning, movement, protected calls, tracelines, HTTP, and file I/O. See the WGG API documentation.volvox— the shared framework table threaded through every file. It is the bus for all cross-file state and services.
Main.lua loads last and starts the runtime via volvox:Init().
Explore the docs
Installation
Get LootRoute loading through WGG.
Quickstart
Open the settings window and start your first gathering run.
Architecture
Load order, the runtime contract, and how the layers fit together.
LootRoute bot
The state machine, routes, node databases, and configuration.
Framework reference
Full API reference for every
volvox.* service.Development
Static tooling, conventions, and the release process.
Authoritative external references
| Reference | Use for |
|---|---|
| WGG API docs | Every unlocker call — names, parameters, returns, failure behavior |
| Wowpedia WoW API | Standard World of Warcraft API functions |
| Wowhead | Every numeric game ID — items, GameObjects, spells, NPCs, zones |
.png?fit=max&auto=format&n=yZatCT6YQ7S22QWv&q=85&s=bb502db827d4362d1268445c3b70d21d)