Files
BT411/players/README.txt
T
arcattackandClaude Opus 4.8 d53fcf61ad BT_STEAM restored as THE compile gate (license) -- default OFF
The unification flattened BT_STEAM into the always-on exe; the user flagged
the constraint that makes it the one legitimate compile gate: the Steamworks
SDK license bars a public release with Steam inside, so a release build must
exclude it entirely.

- CMakeLists: option(BT_STEAM OFF) restored around the Steamworks block --
  an OFF configure touches no SDK headers, no steam_api.lib, no DLL copy.
  BT_GLASS stays retired (always defined); ONE build dir either way.
  Dev checkout: build/ configured once with -DBT_STEAM=ON.
- mkdist: reads BT_STEAM from build/CMakeCache.txt.  Steam-OFF zips exclude
  play_steam.bat + steam_api.dll (explicitly filtering a STALE DLL left by
  an earlier ON build), strip the README steam section ({STEAM} line
  markers), and take a -nosteam name suffix so the flavors never clobber
  (found live: both stamped 4.11.436 and the release zip overwrote the dev
  zip).

Verified both flavors:
  ON  (dev build):  steam smoke degrades to Winsock without the client;
      zip carries play_steam.bat + steam_api.dll + README steam lines.
  OFF (scratch build-relcheck, deleted after): 0 compile errors; exe dir =
      btl4.exe + OpenAL32.dll only; boots + simulates; BT_STEAM_NET=1 inert
      (transport not in the binary); end-to-end zip has zero steam bits and
      a clean README.

KB: context/glass-cockpit.md unified-build section records the license gate.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-21 10:40:03 -05:00

39 lines
1.9 KiB
Plaintext

BattleTech {VERSION} -- multiplayer client
==========================================
IMPORTANT: FULLY EXTRACT this zip first (right-click - Extract All).
Do NOT run anything from inside the zip. The .bat files must sit next
to the 'content' and 'build' folders.
TO JOIN AN INTERNET GAME: double-click join.bat
(waits for the operator's session if it's not up yet)
TO JOIN A LAN GAME: double-click join_lan.bat (operator's LAN)
SINGLE-PLAYER PRACTICE: double-click play_solo.bat (no network)
{STEAM}STEAM INTERNET PLAY: double-click play_steam.bat (EXPERIMENTAL --
{STEAM} needs the Steam client running; host or join from the menu)
Your seat and mech are assigned automatically by the operator.
If the game closes unexpectedly, send the operator content\join.log.
You start INSIDE the cockpit with the pod's MFD panels composited
around the view (one window). The red MFD buttons, radar rails and
joystick buttons are all MOUSE-CLICKABLE -- right-click a button to
latch it held. Press V any time to toggle the external camera.
CONTROLS (keyboard):
W/S or Up/Down ....... throttle lever X / NumPad5 ... all stop
A/D or Left/Right .... turn pedals Alt ........... reverse thrust
Q/E .................. torso twist R/F ........... torso aim
NumPad 8/2/4/6 ....... torso aim/twist (alt) Shift ......... throttle up
1 or Space ........... main trigger 2 ............. middle thumb
3 or Ctrl ............ upper thumb (missiles) 4 ............ pinky
V view | B look-behind | M control mode | N schematic | J/K/L MFD pages
G (hold) + fire key .. regroup a weapon onto that trigger -- or hold a
weapon panel's red PROGRAM button with the mouse and tap a fire key;
the joystick diagram on the panel shows the binding live.
An Xbox controller works out of the box. Rebind keys in
content\bindings.txt (regenerates with defaults if deleted).
This build: {VERSION}. Private -- do not redistribute.