Thoughts on the Interpreter's Script Command

[Zeriab]

Curiously, I can't stop wondering why are you so fixated on this topic.  Not intending to sound harsh at all.

DerVVulfman sent me a PM on this subject which I just discovered today. That + it being a fun excuse to dig into the Ruby interpreter code 

Also,

Q: Has anybody else posted anything like this before?

Me finding a post I made here 15 years ago about this topic answers this 

As per definition and implementations a falsey object in Ruby is either false or nil. A truthy value is any value that is neither false nor nil.
Note: false is a falsey value. false is equal to false. nil is a falsey value. nil is not equal to false.

(...)
Regarding the command_355 stuff, I do understand your desire to add the waiting time but I don't share it. My variant is inspired by VX ACE where any result of the script event command evaluation does NOT become an integral part of the interpretation mechanism. Meaning that it won't stop executing it just because it returned a falsey value like it does in XP.

Incorrect. It must specifically be false and the script call must not contain multiple lines.
You can verify this theory by starting a fresh new RMXP project and running these event commands and see both will show Hello followed by World!
         

Try running a single script line with false and the World! text will never be displayed.
   

YET, I want to add one final thing that I've missed so far. In Ruby simply returning a variable's or constant's value is also a valid test, just as good as var == true or var == false or even !var .

var == true, var == false and !var all evaluates to either true or false.
Returning the value returns the value. Maybe it's used later in a test, maybe not. Doesn't matter from the perspective of statement

RMXP Devs having multiple bugfix options doesn't sounds like a bad deal ^^
*hugs*
 - Zeriab