Glad you found the issue Clark! Thanks so much for taking the time.
There is a problem with the state file not getting saved for me. After I do the "load robutils.e", I want to run the "custom-init" which does modify the state file (setting some "def" variables). I want to do this from my script with "-p custom-init" (after the "-p load robutils.e") so that I don't have to explain to new users how to do this initialization on their own, I want it done automatically.
Is there a way to use -p and run multiple commands? Because currently I first do "-p load robutils.e" with no state file, then I do the "-p custom-init", but the 2nd "-p custom-init" won't save to the state file which is not desired (SE won't be configured the way I want for a new user). If I could do BOTH "load robutils.e" and "custom-init" with one invocation of SE instead of 2, then the settings could be saved to the state file accomplishing what I need.
Another issue is that if I run "custom-init" manually when SE first comes up with my new configuration, I get an error message: "command not allowed when no edit windows present", but it does not tell me which command. Perhaps this is also a reason the "-p custom-init" is not working? I can spend some time figuring out which command requires an edit window. But would there be a way with 1 invocation of SE do "load robutils.e", open an editor window, "custom-init" all automatically (scripted) without any user interaction, and be able to save to the state file?
Finally, even if you hotfix this, I understand the hotfixes go into the configuration directory. Since a new user doesn't have a configuration directory and I am creating a new one for them, does it mean I need to include the hotfixes when I create the new configuration directory for them? How to do that (unzip the file and put it somewhere)? Or export the configuration again from my initial config and it will contain the hotfixes in it?