join.bat + join_lan.bat + the btoperator.py generator template now prefer build-glass\Release\btl4.exe when present and set BT_PLATFORM=glass with it -- so MP sessions on a dev checkout get PadRIO (mouse-clickable cockpit buttons: trigger config, MFD banks, radar rails) and the bindings.txt keymap, identical to solo play. Player zips (which ship only build\) fall back to the pod build exactly as before. Verified: 2-node loopback MP smoke on the GLASS build (the documented procedure: A -egg MP.EGG -net 1501 + B -net 1601 + tools/btconsole.py) -- both nodes cross-connected (GameMachineHost 1502/1602), ~150 sim ticks each, no errors. btoperator.py syntax-checked; regenerated bats carry the same guard. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
46 lines
1.6 KiB
Batchfile
46 lines
1.6 KiB
Batchfile
@echo off
|
|
rem BT411 -- join the operator's LAN game.
|
|
rem BT_RELAY = the operator PC's LAN IP + console port (auto-discovery was
|
|
rem unreliable on this network, so it is pinned). If the operator's IP changes,
|
|
rem update the address below (find it on the operator PC with `ipconfig`).
|
|
rem Joining over the INTERNET? Use join.bat instead.
|
|
cd /d %~dp0
|
|
rem Prefer the GLASS build when present (dev checkout): PadRIO makes the
|
|
rem cockpit surround's buttons mouse-clickable (trigger config etc.). The
|
|
rem pod build renders the same cockpit but clicks are a no-op there; player
|
|
rem zips ship only build\.
|
|
set GAME=build\Release\btl4.exe
|
|
if exist "build-glass\Release\btl4.exe" (
|
|
set GAME=build-glass\Release\btl4.exe
|
|
set BT_PLATFORM=glass
|
|
)
|
|
if not exist "%GAME%" goto badpath
|
|
if not exist "content\OPERATOR.EGG" goto badpath
|
|
set BT_RELAY=10.0.0.46:1500
|
|
set BT_LOG=join.log
|
|
set BT_START_INSIDE=1
|
|
set BT_DEV_GAUGES=1
|
|
cd content
|
|
..\%GAME% -egg OPERATOR.EGG -net 1501
|
|
echo.
|
|
echo The game has exited. If you did NOT quit on purpose
|
|
echo (crash, or it never connected), send the operator the
|
|
echo file content\join.log so they can see what happened.
|
|
echo Otherwise the session may not be up yet -- try again.
|
|
pause
|
|
exit /b
|
|
:badpath
|
|
echo.
|
|
echo ==================================================
|
|
echo ERROR: this file is not in the right place.
|
|
echo.
|
|
echo It must sit in the EXTRACTED game folder, next to
|
|
echo the 'content' and 'build' folders.
|
|
echo.
|
|
echo Fix: right-click the .zip - Extract All, open the
|
|
echo extracted folder, and run this file from THERE.
|
|
echo (Do NOT run it from inside the zip.)
|
|
echo ==================================================
|
|
echo.
|
|
pause
|