Remote Hosting Guide

A Local Game Bridge. A Remote AI Host.

Current limit: LORKHAN's game bridge accepts loopback addresses only. The complete-stack CHIM, STOBE, and Dialectic remote-server layouts do not apply to OpenMW. Do not replace the game bridge address with a second PC's LAN address.

1. Get The Local Setup Working

Complete the local installation first. Test typed dialogue, voice output, and microphone input separately. Back up your working configuration before moving a service.

The local profile setup script reads a local DwemerDistro pairing key. Running it unchanged on another PC does not pair that PC with a remote game server.

2. Choose The Service Address

On the AI service PC, run ipconfig and note its Windows LAN IPv4 address. On both PCs, use a trusted Private network. A router DHCP reservation can keep the service address stable.

The packaged local setup uses launcher proxy port 7514. Browser access to a dashboard is separate from game-bridge support. A working remote webpage does not remove the bridge's loopback restriction.

3. Move One AI Service

1. Start your chosen model, TTS, or STT service on the second PC and test it there.
2. Follow that service's instructions to listen on a trusted network interface. A service bound to 127.0.0.1 cannot receive requests from another PC.
3. Allow only its required TCP port through the Private firewall, scoped to the gaming PC. If it runs inside WSL, forward the host's LAN port to that service's current WSL address and refresh the target after WSL restarts.
4. Confirm LorkhanServer can reach the service from its own environment.
5. Enter the remote endpoint in the appropriate LorkhanServer connector.
6. Test a short interaction before moving another service.

For LM Studio at 192.168.1.50 on port 1234, the full chat endpoint is:

http://192.168.1.50:1234/v1/chat/completions

Replace the example address and port. Use the separate model app instructions for a desktop model host, or your selected TTS and STT service's setup. Bundled DwemerDistro services are local by default; copying their loopback endpoint onto another PC does not expose them to the LAN.

4. Check Access And Playback

• No connection: verify the service is running, its listening interface, LAN address, and scoped Private firewall rule. Guest Wi-Fi or a VPN can isolate the PCs.
• WSL restart: refresh any direct forwarding target that used the old WSL IPv4 address.
• Port opens, but no reply: test the connector from LorkhanServer. A reachable TCP port does not prove that the model, API path, or credentials work.
• Only speech fails: test TTS and STT separately and inspect the logs.

Keep the service PC awake during play. Test typed dialogue, generated voice, and microphone input separately after each move.

Use a trusted private network and restrict service access. Treat the pairing key like a password. Do not forward the router's internet ports or publish credentials to make a local connection work.

Verification status: the loopback restriction was checked against current source. These are provider-hosting steps, not a remote-client installer. Two-PC provider calls and in-game speech still require validation on your setup.