Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.
EVE University · FC Development Group · Draft
Junior FC Pocket Kit
One page for your first fleets. If you only remember three things: tell people what's happening, broadcast your targets, and keep comms clear. The rest comes with practice.
BEFORE → FORM-UP → UNDOCK → FIGHT → AFTER
1 · Before form-up
  • Pick a doctrine and a rough direction. First fleet? Fly Magic Merlins (MER) and just get out there.
  • Know your doctrine: how it fights and flies at a basic level, and what your newbro options are (in Magic Merlins: everything).
  • Keep pings to a minimum: put your event on the Discord calendar, then ping the day before and once close to form-up. That's all you need; more causes ping fatigue.
  • Ask someone to backseat you as 2IC. Optional: ask an FC to share a fleet template.
  • Join voice 15 min early so people can ask questions before the clock strikes.
2 · Form-up briefing

Read it out, skip whatever your fleet already knows.

  1. "Welcome! Tonight we're flying [doctrine], heading [where], looking for [goal]."
  2. "I need scouts, logi, ewar and links. Who's flying what?"
  3. "Add these to your watchlist: FC [name], 2IC [name], scouts [names], logi [names]."
  4. "First fleet? Say so in chat, you're very welcome. Ask anything, vets will help you out."
  5. "Comms: FC and scouts first. Check check for urgent intel only. If you die, die quietly."
  6. "Clean clone, platinum insurance, repaired, all modules online, rigs fitted, ammo in cargo."
3 · Undock and roam
  • Undock, set safety to yellow, warp to a safe. Test a broadcast. Run a quick drill if the doctrine needs one (MER: anchor up on FC; FLF: test a 7 AU warp; etc.).
  • Pick where to go. Set a destination, or take a filament into nullsec: Signal drops you in busy space, Noise in quiet space.
  • Listen to your scouts, then say what you're going to do before you do it. "We're heading to X. Align to Y, take this warp." A fleet that knows the plan follows it.
4 · In a fight
  • Anchor up or tell people where to go, then call and broadcast your primary, then your secondary. Calling is good, broadcasting is better: nobody can find one target in a list of 30 by ear.
  • Make the call. A bad call is better than no call. Need a second to think? Say "hold", but don't freeze.
5 · After the fleet
  • Post the SRP link and the feedback form, end the Discord event, sort out loot.
  • Ask your 2IC or a vet who stuck around: "What's one thing I should do differently next time?"
  • Write a short AAR: what you planned, what happened, what you'd change. No need for a story-like play-by-play; focus on actionable successes and growth opportunities.

Common calls: Anchor on FC · Prop mods on · Primary / Secondary · Hold gate cloak · Jump jump jump · Scatter (warp off grid) · Check check (urgent intel)

Want more? Yinchi's New FC Guide covers route planning (filaments, Thera/Turnur), reading activity on the map, and every fleet role in detail. Read it once you've got a few fleets under your belt, not before your first. See also FC Development Group and Forming fleets in EVE University.