vwemirror/TeslaSuite
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Catalog: launch-key convention, TeslaRel410 product, drop vPOD entry

Browse Source 
- Adopt the launch-key convention (documented in the Apps.xml header):
  fresh Guid = product id, first Launch key reuses it, each extra entry
  increments the last hex digit (wrapping F->0). Never a -1 suffix:
  keys parse as System.Guid and silently collapse to Guid.Empty.
- Rewrite BT411 LC/MR + RIOJoy keys to the convention. RP4.11 LC/MR stay
  pinned to the original console's hardcoded Guids (SiteManagement
  constants + diff tests).
- Remove vPOD from the shipped catalog: dev tool, never a console-deployed
  product (README documents the ad-hoc Add Product path instead).
- Add TeslaRel410 (DOSBox-X preservation pods): six entries, BT/RP 4.10 x
  GameClient/LC/MR, all C:\Games\TeslaPod410\pod-launch.exe with mode
  bt/rp. LC/MR boot identically (role assigned via egg hostType) and no
  {res} token (output size fixed per rig at postinstall).
- CatalogTests: now 5 products / 14 entries; full diff suite 106/106.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Cyd
2026-07-11 17:21:00 -05:00
co-authored by Claude Fable 5
parent 8730b9b966
commit eefb8054e0
3 changed files with 101 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Console/RedPlanet/Apps.xml
+53 -23
View File
@@ -27,6 +27,15 @@
To add a product, append a <Product> with one <Launch>. exe must live under
the install directory the package extracts to (currently C:\Games\...).
Key convention: generate one fresh Guid for the product id; the first
<Launch> reuses it as its key, and each additional <Launch> increments the
LAST HEX DIGIT of that Guid (+1, +2, ..., wrapping F->0). Do NOT append
"-1"/"-2" to the string: keys are parsed as System.Guid and a suffixed
string silently collapses to Guid.Empty. Exception: Red Planet 4.11's LC/MR
keys predate the convention and are pinned to the original console's
hardcoded Guids (SiteManagement.RPLCAppGuid/RPMRAppGuid + the diff tests);
do not change them.
-->
<AppCatalog>
<Product id="7D241B1F-AB6D-4e08-9C20-12294E743D94"
@@ -66,13 +75,13 @@
args="-net 1501{res}"
autoRestart="true"
hostType="GameClient" />
<Launch key="D393711A-EDA0-48B2-82A0-89DF12B768AF"
<Launch key="F4C957FD-72F7-4C5F-8971-28095007E8D0"
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"
<Launch key="F4C957FD-72F7-4C5F-8971-28095007E8D1"
displayName="BattleTech 4.11 MR"
exe="C:\Games\BT411\btl4.exe"
args="-net 1501{res} -mr"
@@ -104,7 +113,7 @@
name="RIOJoy"
menuText="RIOJoy..."
hostTypeDialog="false">
<Launch key="FE83E212-45DF-48F9-848E-0B3CEE0692A3"
<Launch key="87FBC2E6-6359-4EF4-96A5-DF157823CFF6"
displayName="RIOJoy"
exe="C:\Games\RIOJoy\app\RioJoy.Tray.exe"
args=""
@@ -112,31 +121,52 @@
hostType="None" />
</Product>
<!-- vPOD - virtual pod / game-client stand-in for testing the game consoles
(vPOD\ at the repo root). Speaks Munga on 1501 like a real
rpl4opt.exe/btl4.exe and reports either ApplicationID (toggled live in
its window). Deploy it to a pod exactly like a real client; the package
(vPOD\dist\vPOD.zip, built by pack.ps1) extracts to C:\Games\vPOD. -->
<Product id="0041C870-6E5E-4F3B-9782-F94F2F76F21D"
name="vPOD (Virtual Pod)"
menuText="vPOD (Virtual Pod)..."
<!-- TeslaRel410 - the DOSBox-X preservation pods (C:\VWE\TeslaRel410 repo).
The package (emulator\dist\TeslaPod410.zip, built by deploy\package.ps1)
extracts to C:\Games (postinstall.bat + TeslaPod410\); pod-launch.exe is
the single supervising entry point and the mode arg ("bt"/"rp") selects
the game. Camera ship and live mission review are NOT separate modes in
4.10 (the console assigns the role per IP via the egg hostType), so the
LC/MR entries boot identically and differ only by catalog role. No {res}
token: DOSBox output size is fixed per rig at install time. -->
<Product id="135019C7-2C2F-4C38-96BE-C7DB39994AB0"
name="TeslaRel410"
menuText="TeslaRel410..."
hostTypeDialog="true">
<Launch key="0041C870-6E5E-4F3B-9782-F94F2F76F21D"
displayName="vPOD"
exe="C:\Games\vPOD\vPOD.exe"
args="-net 1501{res}"
<Launch key="135019C7-2C2F-4C38-96BE-C7DB39994AB0"
displayName="BT4.10"
exe="C:\Games\TeslaPod410\pod-launch.exe"
args="bt"
autoRestart="true"
hostType="GameClient" />
<Launch key="EA0D4129-8950-428D-8399-E6A77D2D566A"
displayName="vPOD LC"
exe="C:\Games\vPOD\vPOD.exe"
args="-net 1501{res} -lc"
<Launch key="135019C7-2C2F-4C38-96BE-C7DB39994AB1"
displayName="BT4.10 LC"
exe="C:\Games\TeslaPod410\pod-launch.exe"
args="bt"
autoRestart="true"
hostType="LiveCamera" />
<Launch key="FC7CE34E-F4FE-4218-84CD-B13A6FA58E57"
displayName="vPOD MR"
exe="C:\Games\vPOD\vPOD.exe"
args="-net 1501{res} -mr"
<Launch key="135019C7-2C2F-4C38-96BE-C7DB39994AB2"
displayName="BT4.10 MR"
exe="C:\Games\TeslaPod410\pod-launch.exe"
args="bt"
autoRestart="true"
hostType="MissionReview" />
<Launch key="135019C7-2C2F-4C38-96BE-C7DB39994AB3"
displayName="RP4.10"
exe="C:\Games\TeslaPod410\pod-launch.exe"
args="rp"
autoRestart="true"
hostType="GameClient" />
<Launch key="135019C7-2C2F-4C38-96BE-C7DB39994AB4"
displayName="RP4.10 LC"
exe="C:\Games\TeslaPod410\pod-launch.exe"
args="rp"
autoRestart="true"
hostType="LiveCamera" />
<Launch key="135019C7-2C2F-4C38-96BE-C7DB39994AB5"
displayName="RP4.10 MR"
exe="C:\Games\TeslaPod410\pod-launch.exe"
args="rp"
autoRestart="true"
hostType="MissionReview" />
</Product>