Files
TeslaSuite/Console/RedPlanet/Apps.xml
T
CydandClaude Fable 5 18d787bdd5 BattleTech results printing, defaults dialog, and BT411 catalog (BT port phase 4)
Completes the BattleTech console feature to parity with Red Planet:

- BTPrintDocument: the per-pilot landscape score sheet (mech portrait,
  placing, kill/death/damage stats, randomized mission-highlights narrative,
  pilot-vs-pilot damage matrix, place-over-time chart), mirroring
  RPPrintDocument minus the football/lap/boost/score-zone concepts. Wired into
  BTGame (Auto Print checkbox + Print Last Mission button) and the shell's File
  menu (BT Mission Print Preview / Print BT Mission, loading .btm files).
- BTStrings(.xml): the BT mission-highlight narrative pools (damage tiers,
  kill, death-without-honor, recap), loaded from BattleTech\BTStrings.xml like
  RPStrings.
- BTDefaultsDialog: two-column (Free For All / No Return) editor for the BT
  operator defaults, reachable from Settings (Change/Import/Export BattleTech
  Defaults). Verified via UI Automation: opens with all 18 option combos
  populated.
- Apps.xml: the BattleTech 4.11 product (btl4.exe on the shared RP411 engine,
  same -net/-res/-lc/-mr command line; deploys to C:\Games\BT411) with Game
  Client / Live Camera / Mission Review launch entries. CatalogTests updated to
  4 products / 8 entries plus the three new BT entry assertions.

Role model spelling corrected to "noreturn": the Mac Console.ini tag and the
game's BTL4.RES role resource are dfltrole/NoReturn; the 4.10 console's eggs
emitted a broken "noretun" that cannot resolve against the RES. BTGoldenEggTests
and BTConfig.xml updated accordingly.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-07 23:04:03 -05:00

115 lines
5.0 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<!--
Tesla Console product catalog.
This file is the single source of truth for installable products and the
launch entries each one registers on a pod. It replaces the products that
were previously hardcoded in SiteManagement.cs.
Element/attribute reference:
<Product id = install/product key (Guid) used while transferring the package
name = friendly product name (used in menu + status text)
menuText = exact text shown in the Install Product submenu
hostTypeDialog = "true" to prompt for resolution + roles
(Game Client / Live Camera / Mission Review),
"false" to register all launch entries as-is>
<Launch key = launch entry Guid registered on the pod (LaunchData.LaunchKey)
displayName = name shown in the pod's app list
exe = absolute path to the executable on the pod
args = command-line arguments; "{res}" expands to " -res W H"
when a custom resolution was chosen, otherwise to ""
workingDirectory = optional; defaults to the directory of exe
autoRestart = "true"/"false"
hostType = GameClient | LiveCamera | MissionReview | None
(only meaningful when hostTypeDialog="true"; an entry
is registered only if its role was selected) />
</Product>
To add a product, append a <Product> with one <Launch>. exe must live under
the install directory the package extracts to (currently C:\Games\...).
-->
<AppCatalog>
<Product id="7D241B1F-AB6D-4e08-9C20-12294E743D94"
name="Red Planet 4.11"
menuText="Red Planet 4.11..."
hostTypeDialog="true">
<Launch key="7D241B1F-AB6D-4e08-9C20-12294E743D94"
displayName="Red Planet 4.11"
exe="C:\Games\RP411\rpl4opt.exe"
args="-net 1501{res}"
autoRestart="true"
hostType="GameClient" />
<Launch key="57A0B3C2-D5CF-46d6-ABED-A8F4A26AB086"
displayName="Red Planet 4.11 LC"
exe="C:\Games\RP411\rpl4opt.exe"
args="-net 1501{res} -lc"
autoRestart="true"
hostType="LiveCamera" />
<Launch key="8F71D5C2-38E4-413c-8E22-88CAD08774D2"
displayName="Red Planet 4.11 MR"
exe="C:\Games\RP411\rpl4opt.exe"
args="-net 1501{res} -mr"
autoRestart="true"
hostType="MissionReview" />
</Product>
<!-- The bt411 Windows port (C:\VWE\BT411 repo; btl4.exe on the shared RP411
engine, same -net/-res/-lc/-mr command line). Deploys to C:\Games\BT411
like RP411 does to C:\Games\RP411. -->
<Product id="F4C957FD-72F7-4C5F-8971-28095007E8DF"
name="BattleTech 4.11"
menuText="BattleTech 4.11..."
hostTypeDialog="true">
<Launch key="F4C957FD-72F7-4C5F-8971-28095007E8DF"
displayName="BattleTech 4.11"
exe="C:\Games\BT411\btl4.exe"
args="-net 1501{res}"
autoRestart="true"
hostType="GameClient" />
<Launch key="D393711A-EDA0-48B2-82A0-89DF12B768AF"
displayName="BattleTech 4.11 LC"
exe="C:\Games\BT411\btl4.exe"
args="-net 1501{res} -lc"
autoRestart="true"
hostType="LiveCamera" />
<Launch key="2E9B8628-9C20-42FB-B070-E9C38D521082"
displayName="BattleTech 4.11 MR"
exe="C:\Games\BT411\btl4.exe"
args="-net 1501{res} -mr"
autoRestart="true"
hostType="MissionReview" />
</Product>
<Product id="CC8500ED-A653-45a7-BEF8-C332D30371A6"
name="BattleTech Firestorm"
menuText="BattleTech Firestorm..."
hostTypeDialog="false">
<Launch key="CC8500ED-A653-45a7-BEF8-C332D30371A6"
displayName="BattleTech Firestorm"
exe="C:\Games\MW4\launcher.exe"
args=""
autoRestart="true"
hostType="None" />
</Product>
<!-- RIOJoy — virtual-gamepad feeder for the cockpit RIO board (separate repo,
net48 framework-dependent). Its dist\RIOJoy-<ver>.zip is purpose-built for
Install Product: extracts to C:\Games (giving postinstall.bat + RIOJoy\),
and the launcher runs postinstall.bat as SYSTEM to install the ViGEmBus
driver. The console + launcher then own RIOJoy's lifecycle: the launch entry
below starts it and autoRestart keeps it alive (no logon auto-start entry).
On uninstall the launcher runs RIOJoy\pre-uninstall.bat (removes ViGEmBus +
config) and deletes C:\Games\RIOJoy. -->
<Product id="87FBC2E6-6359-4EF4-96A5-DF157823CFF6"
name="RIOJoy"
menuText="RIOJoy..."
hostTypeDialog="false">
<Launch key="FE83E212-45DF-48F9-848E-0B3CEE0692A3"
displayName="RIOJoy"
exe="C:\Games\RIOJoy\app\RioJoy.Tray.exe"
args=""
autoRestart="true"
hostType="None" />
</Product>
</AppCatalog>