WolfPack.quest
Sign in

The platform · the deep version

How it actually works

Four diagrams and three tables. Every overlay, every dashboard, every integration, and the path one line of your combat log takes from the moment EverQuest writes it to the moment the guild can read it. The diagrams are interactive — use the view switcher inside each one to isolate a path, and search to find a component.

Diagram 1

The whole platform

Four components that ship independently. The agent reads logs on the raider's machine, Mimic draws overlays over the game, the bot merges what everyone uploaded and posts to Discord, and the website is the guild's memory. The dashed line back to the fleet is the part people find surprising: triggers, tuning and a kill switch reach every raider by polling, so the guild can change how the fleet behaves mid-raid without shipping anything.

Diagram 2

One line of your log

The privacy story is a filter, not a promise. Officer chat, tells, group and custom channels are matched on raw bytes before the parser runs, so they are discarded rather than parsed and then withheld — there is nothing in memory to leak. What survives goes to local trackers, which is what your overlays read: nothing you see about your own client depends on the network. Only the shareable remainder joins a durable queue that survives restarts, and the bot merges it with every other raider's view of the same fight.

Diagram 3

How an overlay knows anything

Two local sources with different clocks. The Zeal pipe is fast and shallow — names and health, sub-second, no identity. The combat log is slower and exact: it is the only thing that says who did what to whom. Both land in one tracker layer, and overlays hold no state of their own; they poll the agent and paint. That is why fixing one tracker corrects every window that shows it.

OverlayReads fromWhat it does
DPS + Tank HUDcombat logPer-fight damage, healing and tanking, with pets folded under their owner.
Threat meterlog + ZealPer-target threat per player, with a caution band when melee should back off.
CH chainraid chat, localThe cleric Complete Heal rotation, read from zone chat. Fully local — no round trip, which is how it keeps a 2-second cadence.
TankZeal + relayMain-tank health with exact numbers when the tank runs Mimic, percentage when they do not.
Buff queuelog + relayWho is missing which buff, ordered by same-zone, tank HP and curse counters.
Extended TargetrelayEvery mob the raid is on, sorted by how many raiders are targeting it, with HP and debuffs.
Target Infocatalog + relayThe current target's stats, loot table and landed effects.
Triggerscombat logGuild and personal callouts with countdown timers and text-to-speech.
Charm trackerZeal slot 16Charm break timers, driven by the pet gauge rather than the log.
Pet trackerlog + ZealSummoned pet health, buffs and uptime.
Command Centereverything localThe one-window raid board: mana, discipline timers, rez queue, roll sets, cures.
Melodycombat logBard song rotation, detected from the Zeal casting label.
/whocombat logThe last /who you ran, plus everyone seen in the zone recently.
PoP raid guideguide contentEncounter-by-encounter raid guide, pinned beside the fight.
Zeal healththe pipe itselfDiagnostic surface: is the pipe connected, what is it sending, why not.

Every overlay carries the same furniture: a ✕ to hide it, a ✥ to drag it, a right-click menu for size presets, and a hover handshake so its buttons work even though a locked overlay is click-through to the game.

Diagram 4

What the bot talks to

Three of these are somebody else's server, and one of them is a guild member's own AWS bill — which is why outbound calls carry a per-minute budget, a shared cache so N clients cost one upstream call, and a kill switch that works without a deploy. Nothing pushes into us except the agent fleet, over a single bearer-authenticated surface with per-uploader admission budgets.

IntegrationKindWhat it is for
Discordbot + OAuthThe bot is a Discord client; the website signs in through Discord and inherits guild and role membership from it.
SupabasePostgres + authEvery durable fact. Row-level security separates public catalog data from guild data; the bot uses a service role and bypasses it.
Zealnamed pipeThe in-game DLL. Gauges arrive sub-second over a local pipe — health, target, buffs, raid positions.
OpenDKPattendance, bidsSomebody else’s AWS account, so every call is budgeted, cached and killable without a deploy.
Raid-HelpersignupsPulled on a schedule to reconcile who said they were coming with who actually showed up.
Quarm mirrorweekly syncItems, spells, NPCs and loot tables mirrored from the server’s own data by a scheduled job.
GitHubreleasesMimic auto-updates from tagged releases on a stable and a beta channel; the agent hot-swaps along the same line.

Surfaces

Where you actually look at it

Five places, deliberately. The first two run on the raider's own machine and keep working with the network down; the last three are the shared record.

DashboardWhereWhat it shows
Agent dashboardlocalhost:7777Served by the agent itself on the raider’s own machine. Queue depth, trigger fires, charm diagnostics, live parse. Works with the network down.
Mimic windowthe desktop appThe same dashboard inside the Electron shell, plus overlay toggles, UI Studio and settings.
wolfpack.questthe websiteThe durable record: parses, raid boards, loadouts, characters, leaderboards. Discord sign-in, role-gated.
Officer console/admin on the siteTriggers, attendance, encounters, agents, members, audit, feedback, and the mid-raid tuning knobs.
Discord boardsin the guildTimer cards, kill announcements, daily summaries — edited in place, never re-posted.

Diagrams generated with archify ↗ (MIT) from typed JSON kept in the repo at docs/diagrams/. Each one validates against archify's showcase profile with zero errors before it ships.

← back to the platform overviewsource ↗privacy