Hehe sorry I didn’t see this reply right away. Yes I ran into the same situation with the .elf files and how to kill them. I didn’t yet dive into the intricacies of why this is the case for elf files, in fact right now I’m just trying to figure out/learn how these things are compiled in general (with the assistance of AI). It’s incredibly complicated from what I’ve been able to figure out so far… dependency management, plugin additions, etc etc.
So yes for now the CreationStationArcacde is at a solid spot and I will do a post very soon about it. What I started with was a simple re-creation of the core “manage the process” and did it in a bash script called “simpleLaunch”: https://github.com/Kikketer/CreationStationArcade/blob/main/simpleLaunch.sh
BUT I’ve since even taken the CreationStationArcade in the next step:
- The manu “game” shows screen saver and game selections
- When you pick a game in this menu-game it’ll run the standard
control.runProgram(mostly undocumented thing that games can do!) of the selected game (which I believe also kills the menu game). - Create a “reset” button that kills ANY .elf file which is a “kill” type script that runs in the background: https://github.com/Kikketer/CreationStationArcade/blob/main/monitor_kill.py#L153
- And combined with the next step in that kill to then re-launch the menu: https://github.com/Kikketer/CreationStationArcade/blob/main/monitor_kill.py#L167C46-L167C59
So basically you have a menu, push a button to launch a game, play the game… you then must push the reset button (it’s not makeCode arcade button it’s just hard-wired into the raspberry pi that then monitors those pins and hard-kills elf files when pressed and relaunches the menu).
This is a preview post of all the things for this “offline github based arcade machine” 
And man writing it all down like that makes it sound complicated! More complete post to come soon.