99% of all no-scripted runs are essentially done with developer 0. If a run uses dev 1 surely this should be a separate category since it’s an obvious advantage. For example, you can cut off 30 seconds during the IHD with 1000fps. Maybe SDA don’t care if dev is on or off but it surely makes a difference in both scripted and no-scripted runs.
The assumption seems to be thatif it’s scripted, set dev 1, if it’s no-scripted, set dev 0, but in the end we have four different categories.
While I agree with you that it might not be appropriate, what are the basis of disallowing a command just because it’s a no-scripted run rather than a scripted when the command “wait” is simply that, a command, and not a script.
I wouldn’t say changing the recoil in CS is a good comparison to scripts since it’s changing a fundamental value of the game but I understand your point.
“…a script is a list of commands that can be executed without user interaction.”
“A scripting language … automate the execution of tasks that could alternatively be executed one-by-one by a human operator.”
Looking at these definitions, bind MWHEELUP “wait” shouldn’t be considered a script and therefor should be allowed in no-scripted runs. But then again maybe it should be banned for the sake of keeping no-scripted runs the way they are.
bind MWHEELUP “wait;wait” should not be allowed in no-scripted runs since it’s partially automated.
Banning the use of the console and .CFG files seems asinine to me since there’s a lot you can configure but still avoiding making scripts, we just needed a clear definition of what’s allowed.
Maybe we’re getting a bit off topic in this thread btw