Skip to content

Troubleshooting

heft21 edited this page Nov 16, 2026 · 1 revision

"Windows protected your PC"

SmartScreen warns about any program that is not code-signed. Choose More info → Run anyway. To be sure you have the real file, compare its SHA-256 with the one on the release page: certutil -hashfile Drydock.exe SHA256.

Some antivirus programs also flag programs packed the way Drydock.exe is (PyInstaller). If yours does, check the hash, and you can build the exe yourself from source (see the README).

The page says "Start Drydock first"

You opened index.html directly. The page only works when Drydock opens it: double-click Drydock.exe (or Drydock.cmd in a source checkout) and use the page it opens.

"Could not reach the interface"

The Drydock window was closed, so the page has nothing to talk to. Start Drydock again.

"Port 8790 is already in use"

Drydock is already running in another window: use that one, or close it and start again. To run a second copy, start it with Drydock.exe --ui --port 8791.

The index is still building

The first run reads the whole SDK and takes a couple of minutes. Lookups made before it is ready answer "not ready, try again" instead of hanging; the Home page shows when it is done.

The assistant does nothing, or writes JSON instead of acting

The model is not making real tool calls. Use a model with tool calling, and in llama.cpp start the server with --jinja. See Connecting a model.

The assistant stops with "the model returned an error"

Most often the model's context window is too small for the tool list. Load the model with 16,384 tokens of context or more.

My mod loads but does nothing

Ask the assistant to check it, or follow the Diagnose mod guide. The most common cause is an Assets.meta with no definition set, which makes the game skip the whole mod without saying so.

Where are my files?

What Where
Search index, settings, blueprints %LOCALAPPDATA%\se2-mcp
Backups of every file Drydock replaced %LOCALAPPDATA%\se2-mcp\backups
Editor bridge %LOCALAPPDATA%\se2-mcp\bridge\<version>

Still stuck? Open an issue.