F12: The Key with the Misconception.

[kyonides]

A So Called Right to Reply!

The misconception is NOT to call it a bug. You see, when an engine developed to extend ye old RM2K and its cousin RM2K3, they let a committer or participant include C and C++ code slightly based on the RGSS and Ruby code. That was a mistake! It also featured the some stupid F12 reset errors! So it's been definitely the F12 feature inclusion the one that's causing the troubles here.

Since XP they just reset Graphics, Audio, probably even Input, but they never reset Ruby itself! So far it seems Ruby has never included a reset feature ever.  Because of this lack of vision on behalf of the Ruby core team, "DropBrain" just let the C++ side reload the whole bunch of scripts! (Not from memory but by reading the Scripts file once again...) If we were working with pure Ruby or any other OOP scripting language, you'll never reload the scripts!

In this sad scenario they could have done something about that like:

1. Just calling the Main script. (It might even work the best if it has been a hidden script and then do what's mentioned below.)
2. Do what I'm trying to achieve, to implement a simple script call to set the default starting script (the first script after Main) and let the F12 button call a hidden method to set a new value to $scene global variable.
3. Implement any other creative method anybody could come up with!
4. Implement the fake but working solution: just use unless $@ at the end of the alias method.