Please bear with me.... here
I have found some scripts that are very well written but still require user intervention EACH and EVERY time their run.
I understand the reasoning behind the menus you have (no offense meant) dumbed down your scripts to avoid the biatching from icq you script writers get, but lets also look at us users that are getting tired.... of the numbe r of options that we need to reiterate or click through in order to let the script run or a bigger thing whether we are sure. I have developed programs for a few years and we made a joke about how the amount of question that were asked for a typical windows program....
We made some lame joke about how if you moved your mouse a dialog box would pop up and ask are you sure?

Albeit programming has come a long way since I was actively involved the current mindset of "luser friendliness" is making me mad that the programmer can't use some friendly defaults for the questions and not have to ask the same question(s) over and over again.
Where do we draw the line as to usability versus making sure I don't get some lame ICQ that said I was using your script and I went poof.... now fix it.

Save your last menu items...use an bypass switch with processin commands....turn them into a bot for remote loading....problem solved,

Laff, yea... it's not user-friendly at that point. It's programmed ignorance. Badgering the user because the coder doesn't feel like making it smarter.

I use supg's approach in mine. An ansi menu that uses loadvar to pull up the last known settings, and then sets the menu up with those settings. Then all you have to do is adjust whatever and hit "G" to go on.

It starts w/ common, safe defaults. You can then adjust them and when you run the prog it saves your last settings. At that point... if those settings get you killed, cry to yourself.

But writing a public-quality script is a pain in the butt. I don't fault people for skimping on the menu, it's not the most important part.