Frequently asked questions about VerseKit

1. In VerseKit, turn on “Connect to scmdb.net” under Settings → General.
2. Sign in on scmdb.net and choose “Watcher” → “Enable Watcher”.
3. Your browser asks once whether the site may access apps on this device: allow it, let it remember and reload the page.

You do not need to download scmdb's own watcher. It works with LIVE and HOTFIX.

Yes. VerseKit is not digitally signed (yet), so Windows shows “Windows protected your PC”. Click “More info”, then “Run anyway”. The code is public on GitHub, and GitHub builds the files from it itself.

Alt+Shift+V opens and folds the overlay. On Windows, Alt+Shift+R reads the refinery terminal and then opens the storage with the lines it read, and Alt+Shift+B takes the game picture for the signature window at once. Alt+Shift+H puts you into the handle search field of the info bar, Alt+Shift+F brings the main window to the front. All five can be changed or switched off under Settings → Overlay. A single key such as F13 works instead of a combination too.

You can see and change the folder under Settings → Installation & paths (“Folder for your data”). A backup to take along is under Settings → Backup & reset.

Under Settings → Connection & sync, turn on the areas you want (blueprints, storage, hangar, demand, unit storage) and click “Connect”. In the browser you type in a code and sign in with your Basetool account. The “Unit demand” and “Unit storage” pages only appear with this connection.

A false alarm: programs packed into a single file like VerseKit are often flagged by mistake. The checksum shows whether your file is genuine: every version on GitHub comes with SHA256SUMS.txt, and the value there must match your file (on Windows: certutil -hashfile VerseKit-Setup.exe SHA256). If it matches, allow the file in your antivirus.

Download the latest version on the “Download” page and install it over the old one. Your data is kept. If the version still stays old, you are probably starting an old single .exe instead of the installation: start VerseKit from the Start menu.

On its own the button only finds the LUG Helper start script. If you play through Lutris, Heroic or Flatpak, enter your own command under Settings → Installation & paths → “Launch command for Star Citizen”.

Every game patch and every translation update rewrites the game's text file, which drops the details. After a patch VerseKit inserts them again by itself; by hand it is under Game settings → Game → “Insert again”. Then quit Star Citizen completely and start it again, because the game only reads the file at startup. If a second translation tool runs alongside, the two overwrite each other: use only one.

Look at the eye in the overlay bar. Grey means off: click it. Yellow means on but not reading: restart VerseKit once. Green means it is reading. If a number is not recognised, teach it under Mining & Salvage → Mining → “Teach digits”. The scanner is Windows only.

VerseKit counts what appeared in Star Citizen's logs since setup; the game deletes older logs itself. Compare once with the fabricator in the game and tick off what is missing in the blueprint list. If your inventory is already in the Basetool, on scmdb or in a file, bring it in under Settings → Backup & reset → “Import inventory”.

Usually the folder for your data is in OneDrive or somewhere VerseKit may not write to. Under Settings → Installation & paths → “Folder for your data”, choose a folder outside OneDrive, for example on D:.

VerseKit draws at the full resolution of your screen out of the box, there is no switch for it. If the text is too small or too large for you, set it under Settings → Appearance → “Interface size”.