From b07e3285536a0871abfc8912a101bf48a9b82744 Mon Sep 17 00:00:00 2001 From: Cyd Date: Fri, 14 Aug 2026 14:09:33 -0500 Subject: [PATCH] document RP412MFDPROTRUDE for players (handbook + the shipped environ.ini) The knob landed with only a source comment, so a player had no way to find it. Two channels, matching where the sibling display settings already live: - docs/rp412-handbook.html: a row in the "environ.ini - display layout" table beside L4MFDSCALE / L4RADARSCALE / L4RADARPOS, in that table's own voice (what it does, that it is a longer bar rather than a wider button, range and default). - RP_L4/RPL4ENVIRON.cpp: a commented block in the self-documenting default environ.ini the exe lays down on first run, placed at the end of the display-layout section after L4MAPSCALE. Shown commented with an example value (10) since the default 0 means "leave the pod geometry alone" -- uncommenting it is the action. Both state the gotcha the type invites: it takes a NUMBER, and a word parses to 0 (off). Verified: RP_L4 rebuilds clean and the block reads back out of the freshly linked rpl4opt.exe exactly as written, so a first run will lay it down. Co-Authored-By: Claude Opus 4.8 --- RP_L4/RPL4ENVIRON.cpp | 14 ++++++++++++++ docs/rp412-handbook.html | 1 + 2 files changed, 15 insertions(+) diff --git a/RP_L4/RPL4ENVIRON.cpp b/RP_L4/RPL4ENVIRON.cpp index a930ab1..d57474a 100644 --- a/RP_L4/RPL4ENVIRON.cpp +++ b/RP_L4/RPL4ENVIRON.cpp @@ -178,6 +178,20 @@ namespace "L4MAPPOS=LEFT\n" "L4MAPSCALE=100\n" "\n" +"# How far the lit buttons around each display reach past its edge, in\n" +"# EXTRA pixels. The pod's buttons were physical and backlit; on a\n" +"# desktop panel they are a thin bar along the glass edge, and a\n" +"# FLASHING one is easy to miss. This lengthens that bar - the button\n" +"# keeps its width and still reaches the same distance behind the\n" +"# picture, so the display and the click target are unchanged. The red\n" +"# MFD strips and the amber map columns only.\n" +"#\n" +"# 0 - the default - is the pod's own geometry, exactly as it shipped.\n" +"# 1-200 adds that many pixels. Give it a number: a word counts as 0.\n" +"# (BattleTech 4.11 carries the same setting defaulted to 10, where its\n" +"# players asked for it; the two games are tuned separately.)\n" +"#RP412MFDPROTRUDE=10\n" +"\n" "# The Winners Circle: at the end of a race the finishers are stood on\n" "# the award platform in finishing order, with each pilot's callsign on\n" "# the plate beside their spot, and held there for a few seconds before\n" diff --git a/docs/rp412-handbook.html b/docs/rp412-handbook.html index b9a8595..3820ab5 100644 --- a/docs/rp412-handbook.html +++ b/docs/rp412-handbook.html @@ -1133,6 +1133,7 @@ L4MFDSCALE_xxAny one on its own — UL UC UR LL LR. Unset inherits the line above. L4RADARSCALEThe radar alone. It already sits at 1.35× the MFDs. L4RADARPOSCENTER · LEFT · RIGHT · MIDLEFT · MIDRIGHT + RP412MFDPROTRUDEExtra pixels of lit button reaching past each display edge, so a flashing one is easier to catch. A longer bar, not a wider button — the picture and the click target are unchanged. 0–200, default 0 (the pod's own geometry)