Mission Design

Locked in session 2026-04-14.

The mission system infrastructure is complete. What this document defines is the content design - what kinds of missions exist, how they're structured, what makes them interesting, and how they connect to the world's larger story.

Philosophy

Every mission should have a reason. "Kill 10 pirates" is a chore. "The pirates at the Breakwater have been hitting supply ships - three kills won't stop them, but it'll send a message" is a job. The objective is identical. The difference is one sentence of context.

Missions should leave the world slightly different. A completed chain should result in something: a new NPC dialogue option, a lore entry, a standing change, a follow-up unlock. Even a repeatable kill mission should reference what you did last time.

Brevity over depth. Most missions are 2-3 sentences: why you're doing it, where to go, what to expect. Players read this on the board before accepting. They don't re-read it mid-mission. Long descriptions are for story missions, not patrol contracts.

The board is a world, not a task list. A player opening the mission board should feel like they're reading the current situation in the sector - what the factions need, what's going wrong, what's being investigated. It's a snapshot of a living place.

Mission Categories

1. Station Board Missions (Repeatable)

The economic engine. Generated from templates when a player docks. Refresh each dock (or once per hour if staying at station). These are the bread and butter - short, purposeful, calibrated to the economy doc payout targets.

Board composition per station:

• 2–3 Combat missions (kill objectives in this sector)
• 1–2 Explore missions (survey nav points, investigate a location)
• 1–2 Trade/Delivery missions (bring cargo somewhere, escort a ship)
• 0–1 Featured mission (harder, higher payout, usually hints at a chain)

The "featured" slot is what separates a good board from a task list. It changes - sometimes a named mob, sometimes a mysterious survey request, sometimes a delivery with no explanation for why it pays so well.

2. Chain Missions (One-Time Story)

Four subtypes, all using the existing chain_id / prerequisite_id / chain_order system:

3. Event Missions (Triggered)

When a world event fires in a sector, it pushes a special mission to all players currently in that sector (or boarding at that station). Time-limited. Completing it = "I went to the event and contributed."

Structure: single objective - enter_sector for the event zone, or a kill count that the event's own mob kills satisfy. The event completion auto-satisfies the mission for anyone who hit the participation threshold.

4. Daily/Weekly Challenges (Already Built)

Existing system. Not covered here - the challenge system handles these separately from story missions.

The Station Board in Detail

What Players See

On dock, the board shows 6–8 missions, each with:

• Name - short, descriptive, slightly flavored
• Giver - the NPC name (or "Anonymous" for Ashvein Syndicate posts)
• Difficulty - Easy / Medium / Hard (shown as color + label)
• Reward - credit amount, XP type (combat/explore/trade), any item
• Description - 2–3 sentences

Writing Mission Names

Good names are specific and imply context:

• ✓ "Clear the Breakwater" - you know where, you can guess why
• ✓ "Survey the Current Intersection" - mundane but clear
• ✓ "Crux" - a name. That's it. Players want to know why.
• ✗ "Eliminate Threats" - says nothing
• ✗ "Patrol Mission 7" - procedurally generated noise

Writing Mission Descriptions

Three-part structure, all in 2–4 sentences:

1. Context: what's happening in the world that creates this job
2. Task: what you specifically need to do
3. Hook (optional): a detail that makes it feel real or hints at something larger

Example - Combat:

The Scavengers at the Breakwater have been hitting TEC supply ships twice this week. Three kills won't stop them, but it'll make the approach less comfortable for a while. Director Morven says she'll pay for proof of work.

Example - Explore:

One of our survey buoys in the current network stopped transmitting four days ago. Could be drift, could be something else. Get eyes on it and report back.

Example - Trade:

Anonymous posting. Sealed cargo, no manifest, Confluence Station delivery. The credit amount is not a mistake. Don't ask what's in it.

NPC Givers - Named Contacts Per Sector

Named NPC givers create the sense of an inhabited world. Returning to the same contact multiple times builds relationship. When a chain mission comes from Director Strale, players remember Director Strale.

Each sector should have 3–5 named NPCs. Their missions should be consistent with their role and faction. They should have consistent voice.

Example NPC roster for Cinderhold:

The Ashvein Syndicate NPC is never named on the board - their posts just say "Anonymous." Players figure out who it is.

NPC roster design rule: Each sector's NPC roster should reflect the sector's faction presence from the sector-design.md sheets. Don't invent factions that aren't represented in the sector.

Objective Types - Writing Guidelines

kill_mob

• Specify the mob type and implicitly the zone ("the Scavengers at the Breakwater", "the defense drones in the Platform wreckage")
• Count calibration: Easy = 5–8, Medium = 10–20, Hard = 25–40
• Named mob variant (count: 1): the most interesting kill mission. There's a person at the end of it.

visit_nav

• Always give a reason to go: investigation, survey, delivery point, rendezvous
• The nav point name should appear in the mission text if it's a named location
• Count calibration: Easy = 2–3, Medium = 4–6, Hard = 7+ (sequential route missions)
• Sequential route missions (visit in order) create the "navigate through the sector" feeling - players learn the sector's layout

collect_item

• The item should have a name and a reason to exist
• "Collect 5 salvage components" - boring
• "Collect the three black-box recorders from the freighter wrecks in the mid-field" - the same objective with context
• Count calibration: Easy = 3–5, Medium = 5–10, Hard = 10–15

mine_resource

• Best for Trade-oriented players but worth putting on general boards as a "non-combat option"
• Always name the resource and the zone: "Mine 12 energy cells from the Bloom's inner moon gas pockets"
• Count calibration: Easy = 5–10, Medium = 12–20, Hard = 20–30

enter_sector

• Delivery missions, courier missions, "make contact with X in sector Y"
• Almost always chains into another mission at the destination
• Use sparingly for repeatable board missions - better for chain content

reach_level

• Push mission trigger more than a board mission
• Used in the intro chain and class quest lines to gate content by progression

Sector Local Stories (Micro Chains)

One or two contained story chains per sector. 3–5 missions each. Discoverable by playing the board missions - the chain entrance appears as a "featured" slot after the player has done enough work in the sector.

All use existing chain_id / prerequisite_id structure. No new tech needed.

Waygate Station - "The Marker Is Older Than It Should Be"

3 missions. Entrance: survey board mission from a Varath researcher.

1. "Survey Commission" - Survey the navigation marker near the moon (visit_nav ×1). The researcher hired you to get better data than the remote sensors can.
2. "Inconsistent Data" - The marker's signal pattern doesn't match the Varath installation date. Bring the data core to the Meridian contact at the station docking concourse (collect_item ×1, then enter to deliver).
3. "No Comment" - The Meridian contact confirms the marker predates Varath charting of this region. They decline to say how they know. The researcher is frustrated. You're paid either way.

Reward: credits + Explore XP + lore entry: "The Waygate navigation marker predates Varath settlement of this region by an unknown duration. A Meridian contact confirmed this without explanation."

The Drift - "What They're Feeding On"

4 missions. Entrance: kill mission from the Beacon waypoint.

1. "Clear the Feeding Ground" - Kill 10 Void Drifters in the Current Lanes (kill_mob ×10).
2. "Sample Collection" - Collect tissue samples from 3 drifter corpses (collect_item ×3). The Beacon researcher wants to understand why their feeding behavior changed six months ago.
3. "Current Survey" - Survey the three current intersection nav points (visit_nav ×3). The researcher is looking for an energy source.
4. "Unusual Readings" - The current intersections show anomalous dark matter energy - consistent with a large transit through the region. Bring the survey data to Waygate Station.

Reward: credits + Beacon Network standing + lore entry: "The dark matter currents in The Drift show residual energy signatures consistent with a mass transit event approximately nine months ago."

The Threshold - "The Inspection Racket"

4 missions. Entrance: escort mission from TEC Factor.

1. "Safe Passage" - Escort a TEC freighter through the customs zone (travel objective - protect ship from pirate attention).
2. "The Extortion Problem" - Three pirates flagged the ship under a fake customs protocol. Kill them (kill_mob ×3).
3. "Crux" - The extortion scheme has a name: Crux, operating from the Breakwater Asteroids. Find and kill him (kill_mob ×1, named elite mob).
4. "Loose Threads" - Crux had a paymaster. The equipment on his ship has Ashvein Syndicate firmware. TEC Factor doesn't officially care. But they pass the information on.

Reward: credits + TEC standing + small Ashvein Syndicate standing penalty + unlocks: "Anonymous" contact appears on the Threshold board (Ashvein) - they're more interested in who Crux was working for than in the fact he's dead.

The Wreck Field - "The One Nobody Enters"

4 missions. Entrance: salvage mission from Cut and Run.

1. "Standard Salvage" - Collect 8 salvage components from the mid-field wrecks (collect_item ×8).
2. "Deep Field Survey" - Survey 4 nav points in the deep field (visit_nav ×4). Things in the deep field are older.
3. "What the Salvager Found" - The owner of Cut and Run shows you something recovered near the deep field center. Approach the Unidentified Wreck (visit_nav ×1, the first time any player gets close).
4. "Nothing to Report" - Return to Cut and Run. Nothing happened near the wreck. You were paid. The owner looks like she hasn't slept since she found what she found.

Reward: credits + lore entry: "Unknown Vessel - Origin Unclassified. Registry match: none. Architecture match: none. Sensor contact at 50u produced an anomalous response across all ship systems simultaneously. Duration: 3 seconds. Source: unknown." + push trigger: Meridian quest check (if player has visited both the Waygate marker and the Wreck Field)

The Nursery - "What the Obelisk Remembers"

5 missions. Entrance: Conclave survey mission.

1. "Obelisk Survey" - Survey all 5 nav points around the Ancient Obelisk (visit_nav ×5).
2. "Crystal Sample" - Mine 10 Ancient crystal fragments from the gas giant's ring moon (mine_resource ×10). The Conclave researcher needs them for a dating method.
3. "The Relay on Moon Four" - The relay is active - it's been transmitting for decades and nobody filed a report on it. Survey it (visit_nav ×1). It's Ancient construction.
4. "Frequency Match" - The relay frequency matches the Obelisk. Collect the signal data (collect_item ×1 - a sensor log).
5. "Not Ready to Share" - Bring the signal data to the Conclave waypoint. The researcher thanks you and says the Conclave has been reading this transmission for 200 years. She smiles. She doesn't say anything else.

Reward: credits + Conclave standing + Explore XP + lore entry: "The Obelisk and the relay on moon four are transmitting the same signal on a rotating cipher. The Conclave has been decoding it for two centuries. They have not released their translation."

The Crucible - "Benchmark"

3 missions. Entrance: Vael Cohort combat contract, unusually large payout.

1. "Preliminary" - Kill 20 predators in the Debris Clusters (kill_mob ×20). Vael Cohort wants to know you can handle the field.
2. "The Gauntlet" - Fly the Gauntlet route - all 8 nav points in the Debris Clusters, in sequence (visit_nav ×8, sequential). Time recorded.
3. "On Record" - Return to Crucible Station. Your Gauntlet time is posted. Keth pilots will compare it to theirs. The Vael Cohort contact says nothing - just marks you as "worth contracting again."

Reward: credits + Vael Cohort standing + cosmetic title "Crucible Pilot" with your recorded time + access to harder Vael Cohort contracts

Cinderhold - "The Missing Claim Markers"

5 missions. Entrance: featured slot from both Bastion Arms and Stratum Corp simultaneously - rare double-listing.

1. "Contested Boundary" - Survey all 5 claim marker nav points in the Contested Belt (visit_nav ×5). Both Strale and Morven claim markers have been moved.
2. "The Vandals" - Kill the claim jumpers operating in the Contested Belt (kill_mob ×10).
3. "Communications Equipment" - Collect 3 comms devices from the kill site (collect_item ×3). Non-standard hardware.
4. "Who Made This" - TEC Factor Jorin runs the hardware. Ashvein Syndicate firmware. Someone is systematically escalating the corporate dispute.
5. "Your Call" - You can report this to Strale (Bastion Arms standing), to Morven (Stratum Corp standing), to Jorin (TEC standing), or sell it to the anonymous contact. Choice point.

Reward: credits + standing with chosen recipient + lore: "The Contested Belt claim disputes have been deliberately escalated by an outside party. The goal appears to be preventing both corporations from cooperating long enough to notice something else." + intro to Ashfall chain

Ashfall - "What the Platform Knows"

5 missions. Entrance: Stratum Corp safety audit contract (appears after Cinderhold chain completion).

1. "Approach Survey" - Survey the outer platform structure (visit_nav ×2). Confirm the access corridors are still navigable.
2. "Automated Hazard" - The platform's security drones never received the shutdown order. Kill them (kill_mob ×15).
3. "Section A Logs" - Collect the first two data logs from the accessible sections (collect_item ×2).
4. "The Reactor Core" - The final log is in the reactor core section - the section closest to the accident. Clear the drones inside (kill_mob ×8) and collect the reactor log (collect_item ×1).
5. "Mechanical Failure" - Return to Morven. The log says: "Reactor entered cascade response to external stimulus. Cause: unidentified energy source, brief contact, duration unknown. Timestamp: [38 minutes before the explosion]." Morven goes very quiet.

Reward: significant credits + Stratum Corp standing + lore entry: "The Stratum Corp reactor accident forty years ago was triggered by external contact with an unknown energy source. The source made contact for less than a minute. The reactor did not recover." + push: The Forge chain unlocks

The Forge - "The Acquisition"

5 missions. Entrance: Bastion Arms security contract (high standing required).

1. "Supply Convoy" - Protect a Bastion Arms supply convoy from pirate intercept (kill_mob ×18).
2. "Special Cargo" - Escort the convoy to the restricted construction yard (travel objective). The manifest says construction materials. The convoy is escorted by VFN ships for construction materials.
3. "Inside Contact" - Someone inside the restricted zone wants to talk. Navigate to the inner approach (visit_nav ×1). The contact is a VFN officer who disagrees with the secrecy.
4. "The Data" - Collect the data packet the officer prepared (collect_item ×1). It describes what Bastion Arms brought from the Wreck Field: a power source using Ancient crystal architecture, dormant for an estimated 280 years. Reactivated nine months ago.
5. "Deliver or Don't" - Three options: deliver to Director Strale (Bastion Arms standing, they bury the report), deliver to TEC Factor (Beacon Network standing, it gets distributed), sell to Anonymous (Ashvein Syndicate standing, they sell it to the highest bidder). Choice point with significant standing consequences.

Reward: credits + significant standing choice + lore: "The object recovered from the Wreck Field is an Ancient power source that reactivated approximately nine months ago. Bastion Arms is constructing something around it. The VFN considers this a national security matter. One officer disagrees with the secrecy."

Duskhollow - "Earn Your Place"

4 missions. Entrance: Praxar Clan Hall front door - a physical challenge, not a board posting.

1. "The Circuit" - Complete the Sparring Circuit (kill_mob ×15, sequential encounter design).
2. "Worth Talking To" - Praxar Lieutenant Veth challenges you directly. Beat her in single combat (kill_mob ×1, named elite mob).
3. "The Belt Anomaly" - Veth: something in the Proving Belt doesn't match any known fauna. Survey the outer belt (visit_nav ×3).
4. "Unknown Classification" - Kill the anomalous organism (kill_mob ×1, unique unclassified mob variant).

Reward: credits + significant Praxar standing + Keth cultural recognition + lore entry: "The Praxar have no record of this organism variant. Genetic analysis pending. Preliminary findings suggest it arrived in this sector within the last nine months. Origin unknown." + access to Praxar faction chain

Redwatch - "What the Array Is Hearing"

5 missions. Entrance: military intelligence contract from station commander.

1. "Clean Sweep" - Clear the Varath outpost debris zone of drones (kill_mob ×20).
2. "Eighty-Year-Old Files" - Access the outpost's data vault. Collect the unredacted survey report (collect_item ×1). It's dated eighty years before this station was built here.
3. "Then Versus Now" - The old Varath report noted the same anomalous readings the Array is currently picking up. Survey the three Array ping locations (visit_nav ×3).
4. "Pattern Match" - The readings are consistent across eighty years: regular, from the same deep void direction, increasing in intensity.
5. "Sealed Orders" - The station commander gives you a sealed data chip. Deliver it personally to Thornveil Deep. Don't open it.

Reward: credits + Praxar standing + Redwatch mission chain complete flag + push mission in Thornveil Deep

Thornveil Deep - "The Research They Won't Discuss"

5 missions. Entrance: push from Redwatch chain (data chip delivery).

1. "Through the Veil" - Navigate the veil corridors to the research facility perimeter (visit_nav ×3). The corridors are not marked on standard charts.
2. "The Infiltrators" - Ashveld operatives are attempting to reach the facility. Clear them (kill_mob ×12).
3. "Inside" - The sealed chip from Redwatch grants you access to the facility lobby. Collect the research summary from the terminal inside (collect_item ×1).
4. "The Other Half" - A Praxar researcher contacts you privately outside the mission: "The kill switch sequence has an external activation component. We didn't put it there." She asks you to bring this to the station commander, not to the Praxar council.
5. "Who Tells Whom" - Deliver the research finding to: the station commander (Praxar military), Ashveld operative leader (Ashveld standing, this is exactly what they were trying to find), or keep it and sell it later. Major choice point.

Reward: credits + significant faction standing choice + lore: "The Keth kill switch has an external activation component that predates Keth genetic engineering. Whoever designed the kill switch intended it to be controlled by a party other than the Keth or their creators."

Stellar Reach - "Reading the Currents"

5 missions. Entrance: Conclave research contract.

1. "Current Mapping" - Survey all five dark matter current intersections (visit_nav ×5).
2. "Crystal Sample" - Mine 8 Ancient crystal fragments from the ringed gas giant (mine_resource ×8). The researcher is comparing them to samples from the Nursery.
3. "The Flythrough" - Fly through all five current lanes in a continuous path while the researcher monitors remotely (visit_nav ×5, sequential).
4. "Observation Post Four" - The currents are converging toward a point. Survey Observation Post 4 (visit_nav ×1 - the fourth and most distant Ancient observation post).
5. "The Approach" - Post 4 contains a psionic impression the researcher can read remotely. Her voice changes when she reads it. She pays you. She doesn't explain what the post said.

Reward: credits + Conclave standing + Explore XP + lore entry: "Observation Post 4 contains a Meridian psionic impression dated to approximately 280 years ago. The impression uses the Meridian word for 'the approach' - a term that no current member of the Conclave will define for outsiders."

Riftmark - "Thirty Years of Wrong Measurements"

5 missions. Entrance: dual-faction contract from both Varath Platform Alpha and Conclave Stillwatch.

1. "Platform Survey" - Visit and observe all three Varath research platforms (visit_nav ×3). What are they measuring?
2. "Clear the Interference" - Rift-attracted fauna are disrupting both the Varath and Meridian measurements. Kill them (kill_mob ×18).
3. "The Other Readings" - Collect the Conclave's hidden survey data from their three monitoring drones (collect_item ×3). The Varath don't know these drones exist.
4. "Comparison" - The Varath are measuring the Rift's gravitational signature. The Conclave are measuring a signal the Rift is actively broadcasting. Bring both datasets to the location where the hidden gate signal is strongest (visit_nav ×1 - the player discovers the hidden gate location).
5. "Not a Scar" - Return to Stillwatch. The Conclave researcher says: "The Rift is not a wound left by something passing through. It is a receiver. It was built." She gives you the location of The Sanctum gate, and says you've earned the right to find it yourself.

Reward: credits + Conclave standing + Explore XP + hidden gate to The Sanctum unlocked + major lore: "The Rift was deliberately constructed as a receiver, built by the same civilization responsible for the Abyss Gate. It was designed to detect and record the approach of a specific mass transit event."

Abyss Gate - "What the Vigil Has Seen"

5 missions. Entrance: Conclave Vigil contract (high Conclave standing required).

1. "Channel Survey" - Survey the dark matter channels leading toward the Gate (visit_nav ×4).
2. "Unauthorized Approach" - Corporate expedition ships are attempting to reach the Gate without clearance. Drive them off (kill_mob ×10).
3. "Empty Ships" - Three previous expedition ships are drifting near the Gate perimeter, empty. Investigate and collect their crew logs (collect_item ×3 - one log per ship).
4. "What the Log Says" - The last log entry in each ship is identical, written at the same time, though the ships were 200u apart: "Gate contact established. Evaluating." Then nothing.
5. "Evaluation" - Report to the Vigil Station. The elder on duty says: "You're ready. The Gate knows what you are. If it lets you approach, you may."

Reward: credits + Conclave standing + Abyss Gate transit authorization unlocked + lore: "The Abyss Gate actively evaluates pilots who approach it. Ships that failed evaluation were not destroyed - they were simply stopped. Their crews did not know why they stopped." + push: The Nexus endgame missions begin

The Throat - "The Signal"

3 missions. Entrance: push mission triggered by entering The Throat for the first time.

1. "Survive" - Reach the deep zone nav point (visit_nav ×1). The Throat is hostile. Getting there is the mission.
2. "Detected" - The Signal is transmitting. Survey the three points where it's strongest (visit_nav ×3). It responds differently to your approach each time. The third survey point causes something to happen to your ship's systems.
3. "What You Heard" - Return to the Emergency Beacon Station (if you survive). File a report. What you report, and to whom, is up to you: Meridian Conclave (Conclave standing), Varath VFN (Varath standing), TEC (Beacon Network standing), or no one (small credit reward, no standing).

Reward: varies by choice + lore entry (standard): "Unidentified transmission detected in The Throat. Source unresolved. Signal appears to respond to sensor contact." + Meridian translation (if reported to Conclave): "We have found you." + push missions in all three endgame sectors

Race Arc Outlines

Three large interconnected storylines, one per race. They run through the racial path sectors and converge in the endgame. Each arc is 15–25 missions total, pushed automatically as players progress through the appropriate sectors (using is_push_mission and push_trigger_sector/push_trigger_level).

The sector local stories above are the building blocks. The race arc missions are the connective tissue - they reference what the player found in the local stories and build toward the larger conclusion.

Varath Arc - "The Acquisition"

15 missions across entry, Varath path, and endgame. Required: Varath race.

Act 1 - "Something Was Found" (OL 1–30): Connects Waygate Station local story → Wreck Field local story. A player discovers that the navigation marker at Waygate predates Varath charting, and the Unidentified Wreck in the Wreck Field is architecturally different from anything in the registry. Bastion Arms has been studying the Wreck Field for years. One of their acquisition logs is missing.

Act 2 - "The Corporate Conspiracy" (OL 30–65): Connects Cinderhold → Ashfall → The Forge local stories. The corporate rivalry in Cinderhold is being deliberately escalated by an outside party to prevent cooperation. The Ashfall reactor accident was triggered by an unknown energy source. The Forge's restricted zone contains what Bastion Arms brought from the Wreck Field - an Ancient power source that reactivated nine months ago.

Act 3 - "The Classified History" (OL 65–90): In The Shattered Expanse, the player gains access to the Pale Signal research station's classified records. The Reclamation War ended because a third party appeared and both sides withdrew. The VFN has known this for sixty years. The object in The Forge is connected to what was at the Shattered Expanse during the war.

Arc Conclusion: The Varath player learns that the corporate secrecy, the classified military history, and the Ancient acquisition are all connected. Something appeared at the Reclamation War's final battle, watched both sides fight, and left. Eighty years later, one of its objects washed up in the Wreck Field. Nine months ago, it woke up. The race arc ends on the player being given a choice: expose what the VFN knows (Beacon Network standing, information goes public), or help the VFN prepare what they've been building in The Forge without announcing it to the galaxy (VFN standing, something gets built in secret).

Keth Arc - "The Other Half of the Key"

18 missions across entry, Keth path, and endgame. Required: Keth race.

Act 1 - "Anomalies at the Edge" (OL 1–30): The Keth frontier is experiencing anomalous fauna variants that don't match any known species. They're appearing near the sectors where the deep void readings are changing. Nobody is connecting the dots yet. The Praxar aren't sharing what they know with the Ashveld.

Act 2 - "The Kill Switch Secrets" (OL 30–65): Connects Duskhollow → Redwatch → Thornveil Deep local stories. The kill switch research reveals an external activation component no one put there. The Redwatch Array readings match a pattern that appears in the eighty-year-old Varath files from before the station was built. Something has been pinging this sector consistently for at least eighty years.

Act 3 - "The Void's Edge Incursions" (OL 65–90): At Void's Edge, the Long Watch Array logs show seventeen Vrael formations in the past six months. They're not attacking. They're scanning. The Keth player, working with the Praxar commander, discovers that the scan pattern matches Keth genetic profiles - specifically, high-expression individuals. The Vrael are cataloguing who has the strongest genetic expression of the modifications they engineered into the Keth.

Arc Conclusion: The Keth player learns the kill switch has two parts: the internal sequence (Praxar research), and the external activation key (held by whoever designed the Keth). The Vrael. The incursions are not preparation for an invasion. They're taking stock of their asset. The arc ends with the Praxar and Ashveld doing something unprecedented - the player must broker the meeting that gets both factions in the same room before they can act.

Meridian Arc - "What We Forgot, and Why"

22 missions across entry, Meridian path, and endgame. Required: Meridian race.

Act 1 - "The Oldest Memory" (OL 1–30): The psionic impressions in early Explore content (The Drift, The Nursery Obelisk, the Waygate marker) all suggest the Meridian have been in this region longer than their current history records. Each impression is a fragment of something larger. The fragments suggest the Meridian remember forgetting something - a choice that was made, not a loss that happened.

Act 2 - "The Architecture of the Warning" (OL 30–65): Connects Stellar Reach → Riftmark → Abyss Gate local stories. The Rift is a receiver, not a scar. The Abyss Gate evaluates pilots and grants or denies transit. The dark matter currents all point toward the Gate. The Meridian's oldest predecessors built all of this - not to access the other side, but to know when something was coming back from it.

Act 3 - "The Translation" (OL 65–90): At The Nexus and The Sanctum, the player works with the Conclave to attempt the translation that has been failing for two centuries. The vaults in The Sanctum finally open - not because the player forced them, but because the Gate's signal reached them. Inside: the last message sent by the original Meridian before the Sundering. It's addressed to the Vrael. It says: "We have hidden what you're looking for. You will not find it while we live."

Arc Conclusion: The Meridian didn't forget who the Vrael are. They erased it deliberately because knowing posed a risk. The Nexus structure's warming is a response to the signal from beyond the Gate - a reply, after 280 years. The Meridian race arc ends with the player being the first person in two centuries to know what the message actually says, and the Conclave asking: who else do you tell?

Class Quest Lines

Class-specific chains, 10–20 missions, running throughout the game. Gated by required_profession. Pushed at specific OL milestones. Class quest missions appear only for the appropriate profession - no cross-class spoilers.

Tempest - "Blood Challenge"

15 missions. Uses the Blood Challenge exclusive.

A series of escalating 1v1 engagements against named opponents across the galaxy. The Tempest mechanic - single combat, the target cannot flee - is the narrative mechanic. Each duel is a story beat, not just a fight. The chain culminates in a challenge to a Vrael combat drone that appeared at Void's Edge and has killed every pilot who engaged it conventionally. The Tempest's Blood Challenge makes the fight possible. The outcome of the final duel is significant.

Rewards: class-exclusive items after each major duel + the final reward: a weapon modification that can only be made by a pilot who has completed the chain (Crafter-tagged, Tempest-only blueprint).

Wraith - "Ghost Protocols"

12 missions. Uses Phase and Ghost Protocol skills.

A series of infiltration missions that don't appear on any official mission board - pushed directly to the player's log as "anonymous contracts." Each retrieves data that doesn't officially exist. The chain gradually reveals that the Wraith's infiltration abilities are not a natural Keth mutation - they were engineered with a specific operational purpose in mind. The final mission requires the player to choose: destroy that information, or let it reach the Varath who commissioned the research in the first place.

Rewards: class-exclusive sensor mods + a unique ship skin for completing the final mission.

Warden - "The Resonant Chain"

18 missions. Uses Jumpstart exclusive and Resonant abilities.

A recovery mission chain spanning the entire galaxy - each mission retrieves a psionic impression from an Ancient site. The chain requires traveling to the oldest sites across all racial paths. Only the Warden's psionic abilities can safely extract the impressions without damage. The collected impressions form a complete picture of the Meridian's last message before the Sundering - but the Warden receives it in pieces, and the order matters. The chain ends in The Sanctum.

Rewards: most lore-rich class line + Ancient-material components for crafting only a Warden can use.

Wayfinder - "Beyond the Map"

14 missions. Uses Wormhole exclusive and Void Navigation.

A series of exploration missions pushing the edge of the map - each finds a nav point that isn't in any chart, placed by the Ancients for a purpose. The chain uses the Wayfinder's extended sensor range (Void Navigation maxed) to detect nav points that are invisible to all other classes. The final mission leads to a location beyond Void's Edge that only a Wayfinder can reach. What's there is not answered in this chain - it's the hook for future content.

Rewards: highest Explore XP of any class line + access to a hidden sector that only Wayfinder players can reach (one of the "coming" sector slots in the progression).

Vanguard - "Hold the Line"

12 missions. Uses Fortify exclusive and defensive abilities.

A series of defensive operations protecting increasingly critical positions: a mining platform under attack, a station approach, a gate nexus, and finally Confluence Station itself in a classified VFN exercise. The Vanguard doesn't kill the most enemies or discover the most secrets - they make it possible for everyone else to do their work. Each successful defense has a permanent effect on that sector (an NPC survives who would otherwise have died, a facility is protected, a trade route remains open).

Rewards: class-exclusive heavy weapon components + a Vanguard-built defensive structure that players can deploy in the sector where they completed the final mission.

Broker - "Corporate Charter"

16 missions. Uses Corporate Charter exclusive.

A trade negotiation chain building toward a permanent new trade route. Each negotiation stage requires standing with a different faction and uses the Corporate Charter ability to lock in favorable terms. The chain crosses all three racial paths - a Varath deal, a Keth deal, a Meridian deal - and culminates in the New Concordat signing off on a route that benefits all three races. The resulting trade route appears in the game world as a permanent addition: new trade company, new contracts, new economy option for all players.

Rewards: the most economically significant class reward in the game - affects all players, not just Brokers.

Event Mission Integration

When a wave event fires in a sector, push a time-limited mission to all players in that sector:

Format:

"[Event Name] - Respond" Giver: [Faction most affected by the event] A [event type] has been detected in [sector]. Anyone who can help, now. Objective: Enter the event zone and participate. (kill_mob count = participation threshold, or enter_sector to the event position) Deadline: event duration + 10 minutes Reward: Tier-appropriate credits + Event Marks bonus (2× the standard mission Marks reward)

The event auto-satisfies the kill objective as the player naturally fights. Players who don't have the mission get the normal event rewards. Players who do get the bonus Marks.

Faction flavor:

• Combat events: Vael Cohort or the racial military faction posts the mission
• Exploration events (anomaly discovery): Beacon Network or Conclave posts
• Mining disruption events: TEC or the relevant corporate faction
• Vrael events (endgame): VFN, Praxar, and Conclave all post simultaneously

What "Good Mission Text" Looks Like

The existing description field in the missions table supports 2–4 sentences. These guidelines are for whoever authors mission content in the admin tool.

Avoid passive voice. "Scavengers have been detected" → "Scavengers hit two supply ships this week."

Name things. "Go to the asteroid field" → "The Breakwater Asteroids, southwest of the customs checkpoint."

Don't explain the objective twice. The objective tracker does that. The description is the context.

Give the NPC a perspective. "TEC Factor Jorin: The customs racket is bad for everyone on this route, not just the corporations. Help me end it."

Let the mystery be a mystery. If a mission is a hook into something larger, don't explain what that something larger is. "The manifest says medical equipment. The weight is wrong." That's enough.

Short is better than thorough. A player who has read 400 missions will read fast. They want the who, the where, and the why - in that order - and they want it in under 60 words.

Design session: 2026-04-14 Content authoring (actual mission text, NPC names per sector, full chain scripts) is admin tool work, not code work. This document is the design blueprint.