Well, I may consider having some "environment variables" ala DOS - you set it with a function type argument that would extract the game title from the XBE, for example.
I haven't had time to work on it tonight, but I might have some time tomorrow to do some things.
I am also considering some rendering functions for menu ("GUI") actions - rendering a message box, for example, over the previously rendered screen.
Understand: While the "Actions" are executing from a menu selection, everything is suspended. I have to create a routine to handle looking at the input and one to render some simple elements like message boxes and such.
It will be very simple - think along the complexity of a DOS batch file... for now. The BASIC actions will be far more complicated, though. In that case, I plan on spawning the BASIC Actions as their own "process", suspending normal input until they finish (but allowing the skin videos and such to continue executing) - they will be able to bring up dialogs and perform other goodies.
So in the end, there will be two ways to "program" your own menu items: <Action> scripting and <Basic> processes. Basic will be far more powerful... and you'll be able to call "Action" commands from within Basic programs.