How it works

Because I kept getting stuck. A contract sends you somewhere with a one-line objective, the marker is off or the wreck is not where the map says, and you go looking for help. What you find is a video from three patches ago, a forum thread that ends in "fixed in 3.18", and a wiki page that lists the reward but not the one thing you needed to know.

Star Citizen changes with every patch, and the knowledge about it scatters and goes stale. Versefiles is the attempt to keep it in one place and tied to the game build it was written for: the objectives come from the game files themselves, so they are never out of date, and every walkthrough and note says which build it was written on - so you know whether to trust it.

It is a fan project, non-commercial, run by one player with help from those who write things down. If a contract gave you trouble and you figured it out, the next player is one note away from not having that trouble.

Star Citizen ships on several channels at once, and they do not hold the same missions. The switch in the header decides which one this site shows you — it applies to everything: search, mission pages, objectives, counts.

LIVE is the default and the game most people are playing.

PTU is the preview of the coming LIVE phase. It is where you can see what is about to arrive — and where it may still change before it ships.

HOTFIX and others appear on their own as soon as the catalogue holds data for them. Nothing has to be configured for a new channel to show up.

Your choice is yours alone — it changes nothing for anyone else, and the site remembers it on this device.

Ships, ship weapons, components, armor, personal weapons and locations, each as a sortable table and one page per thing. Two sources, kept apart on every page: what the game files themselves say (names, descriptions, the header the game prints on an item) and what the Star Citizen Wiki reads out of the game data (figures, prices, images), marked "wiki". Ships also carry what CIG publishes in its Ship Matrix.

The game-file part arrives with every upload of the tool; the wiki and RSI parts are refreshed automatically when a new LIVE build appears, when the wiki updates, and at least weekly.

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.

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

2. Write. Open any mission and build a walkthrough, or leave a note.

3. Get published. A walkthrough starts as a draft and an admin publishes it. A note is live the moment you save it.

Register

A walkthrough is a list of steps in the order they are done — that order is the walkthrough. There is no separate list of connections to keep in sync.

Steps get a label and a type. Use start and end to bound the run and optional for a detour players can skip. Hover between two steps to insert one in between. Notes, screenshots, video and the link to a real game objective live behind Details on each step.

Branching is opt-in: set a step to decision and it gets its own list of conditions, each pointing at the step it leads to — ore found versus nothing found. Pointing a branch 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.

You are welcome to write on PTU. That is the point of a preview: the guide can be ready on day one. But a preview build is still being worked on, so two things are handled differently.

It gets verified once the build ships. When that build reaches LIVE, the walkthrough is marked as needing verification. Anyone from editor level up — not just admins — can confirm it still matches the shipped game. Whoever wrote it cannot verify their own text; a confirmation by the same person would not be one.

Points come later. Writing on PTU earns its points only once that build has gone live. Not as a penalty — until then it simply is not settled whether the work holds up.

Every published walkthrough can be voted up or down by anyone with an approved account. It is the early-warning system: if a walkthrough stops working, the votes say so before anyone has to complain.

Five downvotes send it back to review — provided there are more against than in favour, so a handful of thumbs-down cannot topple a walkthrough that eighty people found useful. It stays online while it is under review. A silent withdrawal would be worse than a text with a warning on it: whoever needs it right now would be left with an empty page.

Points are never taken back. They are awarded for work done, not for staying correct forever. If a walkthrough goes back to review or is marked outdated, the points stay.

A walkthrough is never deleted. At worst it is marked as outdated — still readable, with a note. Someone put work into it, and even a superseded text still says how it once worked.

Everything on this site can be read by an AI assistant through the Model Context Protocol - Claude, a local model with an MCP-capable client, or an in-game voice copilot such as Wingman AI. The assistant searches missions, reads briefings, objectives, rewards, required items and walkthrough steps, looks up locations and items, and checks which game build the data is from. Read-only, no account, no key.

https://versefiles.com/mcp

Transport: Streamable HTTP. Tools: search_missions, get_mission, get_walkthrough, find_ship, find_location, find_item, list_catalog_filters, get_game_status. Limited to 120 requests a minute per address.

Claude Code: claude mcp add --transport http versefiles https://versefiles.com/mcp
Claude Desktop, Cursor, Wingman AI and others: add a remote MCP server of type "http" with this URL - see their documentation.