Scripting Nightmares

When it comes to scripts, I personally do not like those that directly modify or overwrite the “default” scripts, especially the menus and command positioning. While most are designed as simple plug ‘n play scripts to make their implementation quick, simple and easy, they do invariably interfere.

A prime example is where you have created your menu as you want it, then you “install” someone else’s script, which calls on a new window or scene, and it modifies that script. The result is that sometimes the selection cursor returns to a different position after canceling and returning to the menu.

What this means is that you need to sift through and determine which part of the script is interfering with the positioning and tweak it. It’s not difficult to do, just annoying.

It might be better if aliasing or pushing (or, indeed, some other method of insertion) were used instead – whatever that may be, instead of directly modifying the code. But again, ease-of-use and simple plug ‘n play does make life much simpler, especially with those not too familiar with RGSS. Then, when it comes to actually making the necessary modifications, it helps a little in learning about RGSS.

Even now, I’m not a great scripter per se, although I have learned so much just by studying (and experimenting with) others’ coding. I’ve also studied various resources on Ruby – upon which RGSS is based – so that what needs to be done in my projects can be done efficiently.

Kudos to those who have studied Ruby and RGSS to the point where they have a thorough, working knowledge of it. Ruby script is not hard to learn, just labor-intensive at times to get to that point.