From 39144813a4bfd5ab42bf101cfe8205a66591572e Mon Sep 17 00:00:00 2001 From: Joe DiPrima Date: Thu, 6 Aug 2026 19:20:23 -0500 Subject: [PATCH] pod: kit carries PODTEST.EGG (it was never in the repo) First real new-build drop on the cart exposed it: the kit pushed environ.ini and glass_layout.cfg into the fresh 4.11.817 extract, but runpod.bat launches `-egg PODTEST.EGG` and that mission only ever existed on the pod -- mkdist ships git-TRACKED content only, so the new install had no mission to run. Master copy now sits at C:\bt411\ with the other kit files and podkit.ps1 installs it. Does not affect testers: play_solo/join/play_steam pick their own missions. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Rw7No5wLTpkaUgA3ANbtZZ --- scratchpad/pod/podkit.ps1 | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/scratchpad/pod/podkit.ps1 b/scratchpad/pod/podkit.ps1 index ffe6382..5817cfa 100644 --- a/scratchpad/pod/podkit.ps1 +++ b/scratchpad/pod/podkit.ps1 @@ -36,6 +36,13 @@ if (Test-Path $ini) { # on the next apply, on purpose. One place to look when a panel moves. if (Test-Path $lay) { Copy-Item $lay (Join-Path $Content 'glass_layout.cfg') -Force } +# --- the pod test mission ---------------------------------------------------- +# PODTEST.EGG is NOT in the repo -- it was made on the cart, so a fresh extract +# has no mission for runpod.bat to launch (found the first time a new build was +# dropped: the launcher ran and nothing came up). Carry it in the kit. +$egg = Join-Path $here 'PODTEST.EGG' +if (Test-Path $egg) { Copy-Item $egg (Join-Path $Content 'PODTEST.EGG') -Force } + Write-Output "pod kit applied to $Content" Get-Content $ini | Select-String '^(BT_|L4)' | ForEach-Object { " " + $_.Line } if (Test-Path $lay) { Get-Content (Join-Path $Content 'glass_layout.cfg') | Select-String '^[A-Z]' | ForEach-Object { " " + $_.Line } }