The upload tool

You almost certainly do not need this. The mission data is uploaded by the site operator after each patch. This tool exists as a fallback for the times that does not happen — if the build shown below is behind your game for days, it is worth asking, or running it yourself.

Part of the Versefiles Companion, a small Windows program: with a companion key an admin allowed to upload game data, it reads the mission texts and game data out of your Star Citizen installation and sends them here. That is how this catalogue stays current — the site has no other way to learn what a patch changed.

Currently serving build 12913470 LIVE imported 2026-10-15.

What it does — and what it does not

It reads

The game's own text — mission titles, briefings and objectives. It reads them straight out of Data.p4k, the game archive, so a normal install needs nothing prepared. It also reads build_manifest.id to know which build you are on.

If a third-party launcher has left a loose global.ini next to the install, the tool uses it only when it is newer than the build itself — otherwise it belongs to an older patch and would import stale text under a fresh build number.

It does not

Touch your installation or read your account, your saves or your hangar. It never writes into the game folder. The journal the companion keeps of your sessions is a matter of its own - it goes nowhere without a companion key, see the companion page. The source is a plain PowerShell script — you can read every line before running it.

You need an access key

Uploading needs your companion key with the right to upload game data, which an admin switches on for an approved account. That is not gatekeeping for its own sake: an import replaces the mission data the whole site serves, so it has to be traceable to a person.

Download

File	Size	SHA-256
VersefilesCompanion.cmd version 0.15.1 The Versefiles Companion in one file - uploading is its "Game data" view. Double-click to run, and readable in any text editor before you do.	679 KB	cadc71323467c38a5e1122399d18c7433c9941c4068bd7ae50b9bc93a5d273cb	Download

It keeps itself up to date: it asks this site for a newer version at start, every six hours and right after the game closes, and installs it by itself then - never in the middle of a game, and only a version signed by Versefiles, checked on your PC before anything is replaced. "Install now" in the window does it at once. Switch it off under "Settings" in the window.

Still have QuestGuideUploader.cmd, the upload tool of its own? It updates itself one last time and then points here. The companion takes over its game folder by itself; for the upload it uses your companion key.

One file, put it wherever you like. Verify a download with Get-FileHash datei -Algorithm SHA256 in PowerShell and compare it with the value above. It is a script, not a compiled program — open it in a text editor and you can read every line before running it.

Running it

1. Double-click VersefilesCompanion.cmd. Windows may warn about a downloaded script — that warning is correct and you should only get past it if you trust this site.

2. Under Game data enter your companion key from your profile page and press Save - or under Settings. It is stored in %APPDATA%\Versefiles\companion.json, readable only by your own Windows account — deliberately not next to the script, so the key cannot end up in a repository by accident. Once an admin has allowed the key to upload game data, Game data shows your channels; Check again picks that up without a restart.

3. Pick a channel (LIVE, PTU, HOTFIX, …) and press Upload; Read only shows what it finds without sending anything. Rescan picks up channels the launcher finished downloading meanwhile. When your game has a build the site does not have yet, the companion says so by itself.

The companion looks for the game where the RSI Launcher installed it. If it finds none, pick the StarCitizen folder (the one holding LIVE, PTU, …) with Browse…; it keeps it.

For automation: -GameData -Channel PTU, -GamePath D:\Games\StarCitizen if the game is not where the launcher put it, and -WhatIfOnly to see what would be sent without sending it.

No third-party launcher needed

The mission text lives inside Data.p4k, a 145 GB archive whose entries are ZStandard-compressed. A loose data\Localization\…\global.ini only exists if some third-party launcher put it there — the game itself never writes one.

So the tool reads the archive directly. It carries its own ZStandard decoder, in plain C# inside the script, compiled when it is first needed — no DLL you would have to take on trust. Reading one channel that way takes about half a minute, nearly all of it spent walking the archive's 1.37 million entries. A loose file is used instead when there is one and it is newer than the build — it reads far quicker.

If your installation is modified

Third-party launchers write their own text into global.ini — region hints, blueprint tables, drop chances. That is their curated work, not CIG's data, and republishing it here would be wrong.

The tool detects this and does not refuse: those launchers back up every value before replacing it, so the original text can be reconstructed exactly. It does that on a copy, verifies nothing foreign is left, and only then uploads. Your installation is never touched.