FlyGD Wingman

Wormhole multiboxing toolkit

Fly more clients. Miss less.

Preview every running EVE client, fire wormhole mapping keybinds without leaving the client you're flying, and upload the fight footage you select to your own YouTube channel.

Wingman Previews settings showing appearance, opacity, placement, and shape options for EVE client previews
Wingman Bookmarks settings showing wormhole mapping keybinds such as Grab Sig ID and Set Root
Bookmarks
Wingman Uploader listing recorded fights with age, size, and length columns
Uploading
Wingman Fittings library showing collections beside a list of saved ship fits
Fittings
Primary workflows

Three jobs, equally important

Previews, Bookmarks, and Uploading aren't a main feature and two extras. Each does a distinct job and stays inside its own boundary.

Previews

Keep every client in view

Wingman mirrors each running EVE client into a small always-on-top preview window, so you can watch every account without alt-tabbing between them.

  • Switch which client is active with a click or a hotkey.
  • Set opacity, placement, and lock state per client.
  • An off-by-default setting can minimise the client you switch away from, with per-character exemptions.
  • Boundary: Previews mirrors, activates, and, if you enable that setting, minimises EVE client windows. It never resizes or moves them.

Bookmarks

Wormhole mapping without leaving the keyboard

18 FlyGD keybinds place mapping bookmarks and drive rolling, so you never have to break formation to tag a hole.

  • Bind mapping, rolling, and finisher actions to keys you choose.
  • Bindings are global and scoped to clients you've enabled; per-character keybinds belong to Previews.
  • Boundary: every bookmark action runs from an explicit keypress in an enabled client. Nothing fires on its own.

Uploading

Turn fights into links

OBS or FightRecorder produces the file. You decide what happens to it next.

  • Review, play, rename, or stitch together the recordings you choose.
  • Upload the ones you select to your own YouTube channel.
  • Boundary: Wingman uploads only the recordings you select, and only after you start the upload.
Client awareness

See trouble before it lands on you

Wingman watches your EVE gamelogs for combat starts, warp disruption, and decloaks, and keeps a fleet-wide combat bar so you don't have to tab through every client to know how a fight is going.

  • Background clients stay quiet: sound suppression and filtering on unfocused clients cut down false interruptions.
  • The fleet combat bar reads each character's recent outgoing damage, incoming damage, and EWAR effects from local gamelog activity.
  • A character with no recent log activity shows as missing data, not as zero.
  • Boundary: Wingman does not automate gameplay, and it never moves or resizes an EVE client window.
Alert
Combat start
Alert
Warp disruption
Alert
Decloak
Combat bar reads
DPS out / DPS in / EWAR
Fleet preparation

Prepare the fleet between fights

Profiles, Skills, and Fittings are occasional preparation work, not something you touch mid-fight. One authorization in Settings → Characters covers both Skills and Fittings.

  • Profiles

    Copies a character's or account's EVE settings onto others, taking a backup first so the original can be restored.

  • Skills

    Reads each character's trained skills and current training queue through ESI and compares them with the skill plans you maintain locally, so gaps in fleet readiness show up before you need them.

  • Fittings

    Keeps a local, curated library of fits and copies the ones you choose into the game. Copies are additive: existing in-game fits are never overwritten or removed.

  • Characters

    Settings → Characters authorizes each EVE character once through EVE SSO. Skills and Fittings both use that same authorization.

Fight footage

From recorded fight to shared link

Fight footage is one of Wingman's three primary workflows, not the whole product. OBS or the optional FightRecorder plugin creates the recording; everything after that is under your control.

  1. OBS, or the optional FightRecorder plugin, creates the recording.
  2. Wingman notices the finished file in your recordings folder.
  3. You review, play, rename, or stitch together the recordings you choose.
  4. You upload only the footage you explicitly selected, to your own YouTube channel.
  5. If a Discord webhook is configured, matching combat logs post automatically after a successful upload. A separate "Post the last hour" action is also available on demand.
Trust and data boundaries

Where your data goes

Wingman ships no analytics, no crash reporting, and no usage telemetry. Separate from that: it runs one automatic release check against GitHub on startup, and it reads local EVE gamelogs as part of the client-awareness features above. Neither sends usage data anywhere beyond the destinations below.

Google / YouTube
Desktop OAuth sign-in, token refresh, and uploads of the recordings you select.
CCP
EVE SSO authorization and ESI reads, plus explicit fitting writes you initiate.
GitHub
One automatic Wingman release check on startup, plus explicit Wingman and FightRecorder release downloads or checks you request.
Discord
Posts to the webhook you configure. Nothing is sent if no webhook is set.
Microsoft
A WebView2 runtime download during installation, only if the runtime isn't already on your PC.
FlyGD
No backend. FlyGD never receives your credentials, videos, EVE data, or usage events.
Windows release

Download for Windows

FlyGD Wingman is licensed GPL-3.0-only and developed in the open. Get the current Windows release from GitHub.

  • The core installer runs per-user and does not need administrator rights.
  • Requires Microsoft WebView2. The installer can download and install it if your PC doesn't already have it.
  • The optional FightRecorder OBS plugin may prompt for one UAC elevation if you install it under Program Files.
  • Released builds aren't code-signed, so Windows shows a protection warning on first run. Download only from the project's official GitHub releases page.

Public bug reports and feature requests go to GitHub Issues. For sensitive privacy, account, or security questions, contact technical@zoolanders.vip directly.