Settings

Project Settings > Plugins > HullForge.

Port

Default 8765. The loopback port the editor listens on.

Setting it to 0 makes the operating system pick any free port, which is the most robust option when several editors are open at once. Nothing downstream needs to know: clients discover the real port through the session registry rather than being told it.

Reasons to pin a specific port: a firewall rule, another application already holding 8765, or a policy about which loopback ports may be bound.

Changing the port rebinds immediately. No editor restart, and any connected client picks up the change on its next call.

Start Automatically

Default on. The bridge begins listening as the editor loads.

Turn it off if you would rather start it by hand, then use the console:

HullForge.Start
HullForge.Stop
HullForge.Status

Game Thread Timeout

Default 60 seconds. How long a single tool call may occupy the game thread before it is abandoned.

The right value is workload-dependent. A landscape import legitimately blocks for minutes, while an unresponsive editor during ordinary work should surface quickly rather than hang the client. Raise it if you routinely do heavy imports; lower it if you would rather find out sooner that something is wedged.

How clients find the editor

You do not configure a host or a port anywhere on the client side. Each running editor advertises itself in two places:

File	Purpose
<project>/Saved/HullForge/session.json	Project-local, useful when debugging
%LOCALAPPDATA%/HullForge/sessions/	User-global, how clients discover editors

Both hold a port, a random session token, the project name and path, and a process id. Both are removed when the editor closes, and entries left behind by a crash are swept on the next startup.

This is why several projects can be open at once, and why nothing needs restarting when you open or close one.