arcattackandClaude Fable 5
dfd1894fb9
Field report (first internet-join attempt): both join bats 'hard crash' on the remote machine. Root cause was procedural -- the host session was not running -- but the failure PRESENTATION was the bug: Release Fail() is a bare abort(), so a dead relay = silent process death + instantly-closing console window. - L4NET: the two player-facing dead-ends (LAN discovery no-answer, seat request unreachable/full) now show a MessageBox saying what happened and what to do before exiting (verified live against a dead relay: 'BattleTech -- can't join the game' appears). - join bats: echo + pause after exit so the window stays readable; join_lan.bat header now says it is LAN-only (the remote user ran both -- join_lan can never work over the internet). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
12 lines
429 B
Batchfile
12 lines
429 B
Batchfile
@echo off
|
|
rem BT411 -- join 107.202.218.169's game (internet). Your seat/mech
|
|
rem is assigned automatically by the operator console.
|
|
set BT_RELAY=107.202.218.169:1500
|
|
cd /d %~dp0content
|
|
..\build\Release\btl4.exe -egg OPERATOR.EGG -net 1501
|
|
echo.
|
|
echo The game has exited. If you did NOT quit on purpose,
|
|
echo the session may not be running yet or the server was
|
|
echo unreachable -- check with the operator and try again.
|
|
pause
|