Feature - Implemented User Input w/ timed default

I'm not really sure where this thread should go, so I stuck it here.

I would like to make a request for:

boolean user_confirm(string msg)


in the flavor of:

boolean user_confirm(string msg, int timer, boolean default)


There are instances, when I have sufficient time at night after I get home from work (as well as weekends), that I would like to manually adventure instead of running scripted adventures. I would still like to be able to run the pre-adventuring scripts however. So, I was thinking it would be convenient to have user_confirm() pop up asking if I want to manually adventure or not, but after so many seconds of no response, carry on and return boolean default. A timer value < 1 could mean that the pop up stays until the user physically chooses yes or no (acting like user_confirm() currently does).

That is actually a darn fine idea.

That could also be use in conjunction with various relay scripts that set up more complicated settings; "I see you're using the defaults, would you like to tweak them first?" kind of thing. Seems like a great compromise between "user_confirm() is just an annoyance that breaks the whole point of automating with a script" and "this script really does need to be configured first."

+1

Feature requests go here.

Bump, I like this idea.

r11119