I found a slight optimization to improve the current standard sequence of inputs for a keyboard world creation macro/script, you can remove an input by using Shift+Tab to go back and up through the menu to "Create World" instead of Tab to go forward and down. Assuming that you are using the 70ms delay recommended in the rules, you will save one input and 70ms. Current (Total Delay: 1050ms): Tab Enter Tab Tab Tab Enter Tab Enter Enter Enter Tab Tab Tab Tab Tab Enter Optimized (Total Delay: 980ms): Tab Enter Tab Tab Tab Enter Tab Enter Enter Enter Shift+Tab Shift+Tab Shift+Tab Shift+Tab Enter

Really a tiny optimization, over 1000 runs that's just over a minute, so, certainly worth tweaking your script/macro if you are in the habit of doing several thousand resets a week but probably not worth it if you're doing less than that.

Significantly greater speed should be possible by using mouse inputs, but I am unsure how well that would work with the verification process.

I am writing an AHK script for cooperative speedrunning server resetting that needs to input server ip addresses and the /stop command. I know that there is a 70 ms requirement for inputs but am wondering if something like:

Send, t Sleep, 70 Send, /stop Sleep, 70 Send, {Enter}

Is acceptable (it send the entirety of /stop all at once, as if pasted in) or would it count as multiple inputs and have to be split up like this:

Send, t Sleep, 70 Send, / Sleep, 70 Send, s Sleep, 70 Send, t Sleep, 70 Send, o Sleep, 70 Send, p Sleep, 70 Send, {Enter}

I suspect and hope it is acceptable as it would make the script/macro a heck of a lot easier to write and it would also perform faster.

I would like an answer citing someone of authority or a direct answer from someone of authority.

I am working on a variety of tools, scripts, macros, documentation, and more to help with cooperative speedrunning. I want to release them for the benefit of the community. What open source license do other members of the community (especially developers) think should be used?