Papriko wrote:
Deleting the whole scripts works, but I'd say it's pretty much brute force you use to accomplish the goal.
I'd rather try to use the JECT command in order to get rid of them.
In theory you can make your own cosfile too which does that for you. They are loaded in alphabetic order, so naming it something like zzzzzzzzz_my_own_script.cos would make sure that it is executed at the very end (the scripts must be present in order to be removable again).
I think that bootstrap files are loaded in the following manner: first, a bootstrap folder is chosen alphabetically. Then, the folder's files are processed alphabetically. Then you move to the next folder in the alphabetical order, and so on. In this manner, it may be more practical to create a new bootstrap folder called "090 My Scripts", for instance, and put your scripts there.
As for deleting the whole scripts, I don't think that would work well. First, because the DS variables .cos file is used for many other functions (i.e. breeding limit). And second, because the power to the shee starship .cos file makes a change in the power-up code that may be important; it comments out a change to the max_norns variable effected by the Grendel-Ettin selector pickup, since this variable is no longer applicable in Docking Station (breeding limit and max population are used instead), but the variable may still be read by the engine.