How it works

QuestGuide combines two things: mission data read straight out of the game files, and knowledge written by players. Knowing which is which matters — one is exact but terse, the other is helpful but human.

Where the data comes from

From the game

Mission titles, briefings and objectives are extracted from the localisation files of a clean, unmodified game install after every patch. Nothing here is written by us — including the placeholders like ~mission(Location), which the game fills in per contract.

From players

Walkthroughs and workflows are written by registered contributors. They are never overwritten by an import. When a patch changes a mission, the affected write-ups are flagged for review instead of silently going stale.

Contributing

1. Register. Reading needs no account. Writing does.

2. Wait for approval. An admin unlocks your account by hand. This is a spam guard, not a judgement — it usually takes a day.

3. Write. Open any mission and add a walkthrough, or build a workflow.

4. Get published. Your work starts as a draft. An admin publishes it.

Walkthrough or workflow?

Walkthrough

Free text. Good for context, warnings, loadout advice, payout notes — everything that reads better as prose.

Workflow

A flowchart. Good for missions that branch: build steps, mark the decision points, and label each branch with its condition. The diagram is drawn for you as you type.

Building a workflow

A workflow is steps plus connections.

Steps get a short key (lowercase, dashes), a type and a label. Use start and end to bound the run, decision where the quest branches, and optional for a detour players can skip. A step can be linked to a real game objective, so it stays anchored to the actual contract.

Connections lead from one step to the next. To branch, add several connections out of the same decision step and put the condition in the label — ore found versus nothing found. A connection pointing back at an earlier step makes a loop, which is exactly how retry-until-success missions behave.

Every save keeps the previous version, so nothing is lost if an edit goes wrong.

A note on accuracy

Star Citizen changes constantly. Every mission on this site records which game build it was read from, and every write-up records which version of the mission it was checked against. When those drift apart, the site says so rather than pretending the guide is current.