ok i have stubs in fred, so you can see them, but they wont do jack ****. Here is how they work when completed.
add-background-bitmap will take 9 arguments. 1 string for the bitmap name; 3 for the pitch, bank, heading; 2 for scale; 2 for divisons; and 1 more as an index variable. the index variable is where its stored internally, you need not worry about its value. The index variable is more of an "output" parameter, the only reason it would need to be used would be if you were going to remove that bitmap at a later time using remove-background-bitmap, otherwise you can just make a junk variable and keep using that. What is in CVS now doesn't cover the scale and divisions since i just remembered about that (im a dumbass).
remove-background-bitmap will take 1 argument. The sole argument is the zero-based bitmap index of the bitmap. You can find this by selecting the first bitmap in the background editor dialog and start counting until you reach the one you want to find and remove. Its a pain, so I'll probably add indices in the box so you know for sure which one you're deleting. If you want to delete a bitmap you created using add-background-bitmap, just pass in the value of the variable you used for argument 9.
add-sun-bitmap and remove-sun-bitmap work similarly.
nebula-change-storm will take a single argument. This one shouldn't be too hard to figure out.
nebula-toggle-poof will take two arguments. The first is which poof should be toggled and the second is a boolean expression. If the expression evaulates to true, the poof is turned on. otherwise its turned off. The way i have it setup is that you can have a complex boolean expression determine wheter a poof is turned on or off.
edit: hay who censored $h!t?