History

MALLARD GUARD HISTORY

The Abridged Version, Because the Full Version Involves Too Many Explosions

Established 2952 | Spectrum ID: DUCKED | Headquarters: P.O.N.D., Aqualis V

—-

BEFORE THE GUARD (PRE-2952)

The Mallard Guard did not begin with a plan. It began with two people who were very good at their jobs and needed somewhere to put that.

Daxwell “Wiggleking” Mallard and Krull Darkshine met through UEE Navy service — Krull observed Dax from a professional distance first, the way you notice someone who keeps producing results that shouldn’t be possible and decide you want to understand why. What he found when he looked closer: the chaos was real. The results were also real. Both, somehow, simultaneously. His evaluation report was positive. The footnotes were extensive.

They left the Navy around the same time. The contracting era followed. No name, no structure, no formal arrangement — just two people who had agreed, without stating it plainly, that they were building something. They kept meaning to formalize it. They kept not doing it. The jobs kept coming anyway.

Others joined the network as contracts required more people. Dr. Adrian “DrYinko” Yinkowski — a man whose particular skills and access to information defied reasonable explanation and who nobody looked at too closely, which suited everyone. Kesslan Veyra — who will tell you he’s just a cargo hauler. He is not just a cargo hauler. Nathan “Jonesy” Jones — who appeared at a tense cargo dispute on a commercial station, de-escalated it, got bought drinks, and never entirely left. Carter Percival Gryphon — pulled in by Dax personally, oldest friendship in the organization, stayed for the pay and the gadgets.

By 2952, the contracting network had a reputation. Clients were asking for it by description. The administration was becoming untenable. Krull identified the moment. He always identifies the moment.

—-

THE FOUNDING (2952)

The 0300 Session

The Mallard Guard was formally named at 0300 hours, after 72 hours without sleep, by two people who were running on momentum and the shared certainty that the thing they were building had outgrown the absence of a name.

Krull presented the situation as a conclusion: administrative friction had reached its ceiling, the network’s reputation required something to attach to, the informal arrangement was at its limit. Dax agreed before Krull finished the sentence.

The duck theme was not a decision. It was a convergence. Daxwell Cornelius Mallard. The “Royally Ducked” motto already in circulation from a Navy incident that had followed him out of service. A childhood spent on Pondura IV, where the waterways run wide and the local MIRAI racing team — the Pondura Drakes, one legendary season, decades of mediocrity — had shaped his understanding of loyalty, formation, and the specific stubbornness of committing to something past the point of reason.

A brief note on “Royally Ducked”: during active Navy service, Dax transmitted an honest assessment of a near-catastrophic situation over a monitored channel. A comms officer censored it, substituting “ducked” — the Mallard callsign making the wordplay irresistible. The censored version circulated through Navy channels. A writer with Pondura IV connections published it. The article spread. Dax adopted the phrase immediately and completely. There is a framed copy of the original article in his P.O.N.D. office. He has never explained why it’s there.

At 0300, all of these things arrived in the same place at once. The duck theme crystallized. The paperwork was filed. By the time anyone was rested enough to reconsider, it was already done. The name stuck. So did the team. So did the inexplicable commitment to waterfowl-based branding.

This should have been a warning sign. Nobody treated it as one.

The Framers

The 0300 session was Dax and Krull only. The formalization — the session that built the structure the Guard would actually run on — was a separate event, with Dax, Krull, Yinko, Kesslan, and Jonesy present. They sat down. The Guard was already what it was because of all of them. This session made it official. These five are the Framers: the people who were present when the Mallard Guard became a formal organization rather than a persistent idea.

Carter Gryphon was not present. He became load-bearing anyway. The Vic recognized this eventually. They always do.

—-

BUILDING THE RAFT (2952-2953)

P.O.N.D.

The Mallard Guard needed a home. What it got was P.O.N.D. — Primary Operations Nexus & Datalink — on Aqualis V.

Dax and Krull were both deeply involved in its construction, at a level that rendered the contracted architectural firm largely executory. Krull led the aesthetic and architectural direction. Dax was heavily involved in the engineering systems — he questioned the contracted architects and engineers at length, in detail, and to their considerable frustration. Several engineering decisions were revised as a result. He also insisted the construction model be developed to a standard sufficient for facilities management use as a digital twin. This was frustrating at the time. It is used daily now.

The result is a facility that reflects both of them completely: precise, functional, over-engineered in the interesting ways, and containing a lobby interactive holographic model that Carter built with Dax and Krull — technically impressive, route download feature has never worked, IT ticket open since commissioning, Carter insists it is an IT issue.

The Museum of Questionable Decisions houses Wiggle One, Dax’s retired custom Aegis Gladius, along with documentation of select operational decisions the Guard has collectively decided deserve permanent display. The exhibit grows.

The Vic Forms

The Mallard Guard is led by The Vic — named for the vic formation: the V-shape of birds in flight, each position holding the structure, each draft reducing the resistance for the next.

The Vic is not a rank and not an appointed council. It is the name the Guard gave to the people at its center — the ones who built what they lead, who contribute what they direct. Membership is recognized, not assigned.

Wiggleking	Daxwell Mallard	Supreme Wing Commander, Co-Founder
Darkshine	Krull Darkshine	Director of Tactical Operations, Co-Founder
DrYinko	Dr. Adrian Yinkowski	Director of Intelligence Operations
Kesslan	Kesslan Veyra	Director of Logistics & Medical Operations
Smilin’ Jonesy	Nathan Jones	Director of Security & Internal Affairs
Aluminum	Carter Gryphon	Director of Navigation & Cartography

Six people who should probably not be in charge of anything. The operational record suggests otherwise.

—-

WHERE THINGS STAND (2954)

The Mallard Guard is two years old. It has built multi-role operational capability, a headquarters that functions exactly as intended despite the IT ticket, a culture where professional excellence and deliberate absurdity are treated as the same thing rather than opposites, and a growing archive of operational records that future historians will find either invaluable or deeply confusing.

We take contracts others decline. We complete missions others can’t. We have established, through documented operational results, that the duck theme is not an obstacle to effectiveness. If anything, it filters for exactly the right kind of person.

The field reports in this section are drawn from our operational history. They are written as fiction — names and details adjusted to fit the universe — because some things are too good not to write down and too ours not to share. The events are real. The chaos is accurate. The explosions are accurate.

The lessons are still being learned. Slowly. Explosively.

—-

THE BOTTOM LINE

Born from two people who were building something before they had a name for it. Forged in a 0300 session that nobody planned and nobody could have stopped. Inexplicably, irrevocably duck-themed.

We are not the most traditional organization. We are not the most conventional operators. We are not the ones you call when you want it done by the book.

We are the ones you call when the book doesn’t have a chapter for your situation.

“Service Above the Surface. Loyalty Below the Wake.”

We’re armed. We’re tactical. We’re occasionally on fire.

We don’t duck around.

—-

Mallard Guard | Established 2952 | “Royally Ducked Since Day One”

Manifesto

MALLARD GUARD MANIFESTO

Spectrum ID: DUCKED — Armed. Tactical. Occasionally on fire. We Don’t Duck Around.

WHO WE ARE

We’re six friends who play Star Citizen together. We haul cargo, shoot things, rescue people, mine rocks, and occasionally set something on fire.

Sometimes on purpose.

We’re also duck-themed. Extensively. Unapologetically. We’ve tried to walk this back. There is no walking this back. We’ve made peace with it. It’s honestly the funniest thing that’s ever happened to us as a group, and we’ve leaned into it so hard at this point that the ducks are load-bearing.

HOW IT STARTED

Someone was naming a ship. One duck name led to another. A large language model got involved — usually at work, almost always at work — and 7,000 duck puns later, here we are. The org exists because nobody stopped us in time.

The duck theme isn’t ironic. We’re not winking at you. We committed because it reflects how we actually operate: all in, no half measures, genuine over performative. We don’t do things halfway. That includes waterfowl branding.

WHAT WE ACTUALLY ARE

We show up to complete missions and get paid. We care about succeeding. We’re just equally serious about having fun doing it — which apparently makes us weird to a lot of gaming orgs. We think they’re the weird ones. We’re not going to resolve this.

We’re focused on the job. But then a 20-minute cargo haul becomes a game of catch with a small car. Or someone decides to fly a Pisces through a C2 cargo bay at speed and hope for the best. Or someone — in a moment of inspiration — says “let’s see what happens if we jump a Nursa out of the back of a moving Starlancer TAC above a bunker.”

Spoiler: there are explosions. And a lot of walking.

We weren’t trying to be funny. We’re just not pretending to be robots when we’re actually people who occasionally forget which button does what under pressure.

WHAT KIND OF PEOPLE WE ARE

We’re the kind of people who commit fully to bits we believe in, even when those bits are absurd. Who laugh at inside jokes that make zero sense to outsiders. Who take the work seriously and themselves not at all.

When someone crashes their ship mid-objective, everything stops. We execute an emergency EVA rescue across a space station because apparently that’s more important than the cargo run. Nobody’s respawning on our watch — do you know how long it takes to get six people in the same place in the PU? Then we go back and finish it. That’s not chaos — that’s how we work. Mostly. Often enough.

WHY NOT A BIG ORG

Big orgs have their place. If you want to be pilot #347 in a coordinated fleet operation with a chain of command and a rank structure and someone called High Admiral of something, that exists. Go find it. It’s out there.

What you don’t get there: you actually know the people you fly with. Every mission matters because every person in it matters — there’s no anonymous crew member, no disposable wingman, no one who logs off and nobody notices. When something goes wrong — and it will — it’s your friend’s ship that just exploded, and that’s a completely different experience than watching a number disappear from a roster.

No politics. No ranks. No bureaucracy. Nobody’s angling for a promotion or managing their reputation in a hierarchy. Just people who want to play the game and actually give a damn about the people they’re playing it with.

THE FOUNDING SIX

The Vic are the six people who built this and still fly together.

Wiggleking — The reason we have a duck theme. Also the reason we have an org. Both things are connected.

Darkshine — The reason the org actually functions. Quietly handles everything. Prefers it that way.

DrYinko — Knows things he shouldn’t know. Never explains how. Results always correct.

Kesslan — Will tell you he’s just a cargo hauler. He is not just a cargo hauler.

Jonesy — Late to everything. Somehow always effective. Possibly a miracle. Unclear.

Aluminum — Knows where everything is. Enthusiastic about it. Very enthusiastic about it.

Six people who should probably not be in charge of anything. Somehow it works. The History section explains how. Sort of.

THE LORE

Want to know what it’s actually like to fly with us? Check the History section. The lore there is based on things that genuinely happened — missions, decisions, moments too funny to let disappear into a Discord scroll. One of us, possibly the same person responsible for the duck theme, couldn’t help himself and turned them into fictional field reports. Almost certainly at work. Names, characters, and dialogue may have been tweaked to better fit the universe or really capture the vibe and humor of the event.

The explosions are accurate.

THE DUCK THING IS THE POINT

If you think committing to something absurd is incompatible with being competent, we’re definitely not the org you’re looking for. But if you respect people who are willing to be fully themselves — who commit to what they believe even when it makes no sense to outsiders, who laugh at themselves while still getting the job done — then the duck theme makes perfect sense. Welcome to it.

WHAT WE’RE LOOKING FOR

Not a skill set. Not a playstyle. Just people who feel like they belong in the same Discord as us. The right fit will know pretty quickly whether that’s them.

Armed. Tactical. Occasionally on fire. We don’t duck around.

Spectrum ID: DUCKED | “Royally Ducked Since Day One”

Charter

MALLARD GUARD CHARTER

Spectrum ID: DUCKED — Practical. Honest. What joining actually means.

WHAT WE ACTUALLY DO

Multi-role. Cargo runs, combat, mining, rescue, escort, exploration — whatever the mission needs. Nobody’s assigned a lane. People play what they enjoy and it tends to work out. One of us is quietly excellent at stealth. Someone always handles medical. Cargo runs happen constantly. The 20-minute haul that becomes something else entirely happens at least once a session. We have a compilation of creative docking techniques. It grows regularly.

HOW MISSIONS ACTUALLY WORK

In theory, a well-run squad has a defined composition. A pilot. A medic. Combat roles covered. Someone on sensors. Clear lanes, clear responsibilities, everyone knows their job before boots hit the ground.

In practice: someone shows up in the wrong ship, someone else brought a weapon that’s spectacular but tactically questionable, and the medic is already doing something that isn’t medicine. We adapt. Roles emerge from whoever’s best positioned in the moment rather than whoever was assigned beforehand. It works out more often than it probably should.

We’re not trying to be inefficient. We genuinely want to be a good team and we’re always getting better at it. We just also accept that six different people with six different ideas about the optimal approach are going to produce something that looks less like a doctrine and more like a negotiation. Usually a successful one. Mostly. Often enough.

The goal is always mission success. The path there is subject to revision, improvisation, and at least one decision that nobody will be able to fully explain afterward.

LEADERSHIP — SUCH AS IT IS

The original six are The Vic — loosely the leadership council, practically just the people who know what’s going on. There’s no formal rank structure beyond that. Decisions get made by whoever knows the most about the current situation. It works. Nobody’s entirely sure why.

MEMBERSHIP — WHAT IT ACTUALLY MEANS

Right now we’re a small group of friends who want to find more people like us. We’re not trying to hit a number. We’re looking for fit — specifically, people we’d actually want to play with, because that’s the whole point.

No mandatory hours. No required roles. No activity rankings. Main org or affiliate — we don’t care, and several of us are already in other orgs on other accounts. What tends to happen in practice: this becomes the group you actually play with.

Zero SC experience is fine. You figure it out as you go. The only hard requirements: a Star Citizen account and Discord.

HOW COORDINATION WORKS

Discord. That’s where missions get planned, sessions get called, and everything happens. Two people online? You play together. Need more crew? Post up. Big events that need everyone get scheduled. Everything else is organic. If you’re not checking Discord occasionally, you’ll miss things — we’re not going to hunt you down.

THE REALITY OF PLAYING TOGETHER

You’re going to shoot each other. Accidentally. Someone will lose a ship because of something dumb someone did. You’ll get frustrated. That’s fine. Laugh about it. Give them crap. Poke fun at the decision that cost you both a mission. That’s how we bond.

The line is simple: “frustrated but laughing about it” is friendship. “Still mad next week” is drama. Keep it the first one. Nobody did anything to hurt you. We were all doing something dumb and it went wrong. That’s the game. That’s hanging out.

CODE OF CONDUCT

We keep it simple. There are exactly four rules.

One duck pun per gaming session. This is strictly required and has never once been enforced. We trust you to do the right thing.
Don’t cheat. We’re here to play the game, not break it. If someone else is cheating, adapt and move on — nobody wants to hear about it for the rest of the session.
Griefing is generally frowned upon. Exceptions apply when it is genuinely hilarious, directed at a fellow member who absolutely had it coming, or agreed upon collectively as a group activity. Use your judgment. We believe in you.
Be a Duck not a Dick. We don’t need a Rule 5.

LEAVING — OR NOT REALLY

Once a Mallard Guard, always a Mallard Guard. If you played with us, laughed with us, got shot by us — you’re part of this. Life happens. Games change. People drift. That’s fine.

Started your own org you’re playing with more? Good. Come back and play with us sometime. Better yet — let’s all play together. The raft doesn’t shrink when people step away. It just floats in more directions.

ALLIED ORGS — THE AWC

If you’re running your own org and want to fly with us without merging or switching mains, the door is open. We’re not precious about org lines. Some of the best sessions happen when different groups decide to do something stupid together.

No formal structure, no paperwork, no commitments. Just reach out — message us on Spectrum or drop an application on RSI with a note that you’re looking for an allied org relationship rather than membership. We’ll take it from there.

Think of it as the Aquatic Wing Collective — allies, fellow travelers, and anyone who’s looked at us and thought “I don’t want to join that, but I absolutely want to fly next to it.”

FAIR WARNING — YOU WILL ENCOUNTER

Duck puns (non-negotiable)
Friendly fire (documented)
Creative docking techniques (also documented)
Unscheduled EVA rescues
Getting knocked unconscious mid-op
Casual profanity in frustration and affection (sometimes the same sentence)
No hazard pay (discussed, declined)
Someone on a mission they’re not rostered for

HOW TO JOIN

Apply on RSI. Tell us a bit about yourself — experience, what you like doing in SC, why this seemed like a good idea. Also include your best duck pun. This is required. It will not be considered in evaluating your application. One of us will read it. Most of us probably won’t.

For the purposes of this requirement, other waterfowl, water-adjacent birds, birds you have seen near a puddle, and birds that got wet once are all acceptable alternatives to ducks. We have standards. They are these standards.

If it seems like a good fit, we’ll reach out on Spectrum with the Discord link and go from there.

We’ve been looking for an HR professional to handle this more formally. Apparently none of them want to work for a duck-themed org. Go figure.

Welcome to the flock.

Spectrum ID: DUCKED | Apply on RSI | Main or affiliate: both fine

Mallard Guard / DUCKED