Repository navigation
Getting started
- Windows.
- The Space Engineers 2 Mod SDK, installed from Steam. Drydock finds it by asking Steam where its libraries are.
That is all. Python and everything else Drydock needs are inside Drydock.exe.
Get Drydock.exe from the latest release and put it in any folder you like.
The release page lists the file's SHA-256. To check yours:
certutil -hashfile Drydock.exe SHA256
Double-click Drydock.exe. A console window opens and, a moment later, the workshop opens in your browser.
Keep the console window open while you work. It is Drydock itself; the browser page talks to it. Closing the window stops Drydock.
The first time, Windows SmartScreen may say "Windows protected your PC", because the exe is not code-signed. Choose More info → Run anyway.
Drydock reads the SDK's ~50,000 definition files once and builds a search index of them. On the first run this takes a couple of minutes; the top right of the page shows Building index… until it is done, and lookups made before then say the index is not ready yet instead of hanging. After that it is instant, and it rebuilds itself when you add or remove a mod.
The index, settings and backups live in %LOCALAPPDATA%\se2-mcp, not next to the exe.
Drydock.exe --selftest
Ten checks: it finds the SDK, builds the index, reads a real definition, then makes a mod in a temporary folder, writes into it and audits the result. If all ten pass, everything works.
- Connecting a model, so the assistant can work.
- The workshop, for a tour of the pages.
Drydock, by Heft · github.com/heft21/drydock-se2 · MIT license · not made or endorsed by Keen Software House