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

pack-dist: ship steam_appid.txt so a fresh dist is test-ready

Browse Source 
The packer wipes and rebuilds dist\, which silently discarded the
hand-made steam_appid.txt every repack - and without it SteamAPI_Init
fails and the game quietly falls back to TCP, which is the confusing
symptom testers hit. The dist now ships it (480, Spacewar) alongside
the RP412STEAM=1 environ.ini, so copying the folder to a machine with
Steam running is the whole setup. Test doc updated to match.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Cyd
2026-07-24 20:08:25 -05:00
co-authored by Claude Fable 5
parent 4b25f89e6f
commit 1ba3bde36a
2 changed files with 14 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/STEAM-3-MACHINE-TEST.md
+7 -7
View File
@@ -9,13 +9,13 @@ the first live test.
1. Steam client installed, logged in (different account per machine),
and RUNNING.
2. Copy the `dist\` folder onto the machine.
3. In the dist folder, create `steam_appid.txt` containing exactly:
`480`
(Spacewar, Valve's public dev AppID — replaced by the real AppID
once the store page exists.)
4. Add to `environ.ini`:
`RP412STEAM=1`
5. Start with `start-windowed.bat` as usual.
3. Start with `start-windowed.bat` as usual.
The packed dist already contains `steam_appid.txt` (480 — Spacewar,
Valve's public dev AppID, replaced by the real one once the store page
exists) and ships `RP412STEAM=1` in `environ.ini`. If a machine has an
older dist, check both before blaming the network: a missing appid
file makes SteamAPI_Init fail and the game quietly falls back to TCP.
Sanity check per machine: `rpl4.log` should show
`SteamNetTransport: up as 169.254.x.y (fake ports N console, M game)`.