MAGI'S PROFILE

It's probably Borland Delphi under the hood, but most people just refer to event scripting systems as "point and click".

author=eplipswich
Then it's time you move on to RPG Maker XP and above if you're serious about game making. Because the so-called "scripting" in RM2k/3 is not even true programming language.

Idk, this has always been such a weird argument. RPG Makers with proper scripting systems are by and large more flexible, but it still has a "hobbyists" tool status compared to more robust software. Game development is such a wide field of skills and abilities that you can use any piece of software and it's as serious as you decide to make it.

By the end of my rope I saw so many submissions beneath the site's standards each week that I just started copying and pasting denial responses I had in a document.

e: Before anybody asks what it must have felt like to be so corporate I will tell you: It felt like dying

Parallel process is essentially a "while" loop instruction in traditional programming languages. The problem with these loops whenever we're concerned with using time-sensitive functions is that the loop doesn't care about standing around for them to complete in the way other event triggers would.

Try placing your wait options directly after both the hide and show screen events instead of having them clustered around show screen. Sometimes even RM2K3 gets very touchy about its internal order of operations.

Failing that, try cutting out all your event code until it behaves as expected. This will allow you to (eventually) isolate what is actually causing you grief.

If you just had users agree to install a browser plugin that surveys how many Sword Art Online fan games are in somebody's RPG Maker folder, then you wouldn't even need to disable registrations.

I'm curious if further development on RPG Maker 2003 has halted completely. It's in a good place for most people, but the time of the last update was nearly a year ago and I'm sure some people were hoping for one or two more updates. Still, the changes in the official release are great and are more than most of us could have asked for to begin with.

I think the EULA is specific about Advo's version being a messy can of worms if you choose to go commercial on it. I know some people were knee-deep in using the CGSS/DynRPG plugin, which makes importing into the official release all but impossible.

That brings me kind of to the next point: the PicPointerPatch. I've just modernized this classic feature for the official version, but have had to make changes so owners of the Steam version can enjoy it. The original patch required users to modify both their editor and the runtime, but my "Lite" version only requires the RPG_RT file to be patched. It's a bit more limited as a result, but sacrifices had to be made to ensure broad compatibility.

With these two patches, I think it should bring a very large amount of functionality that has been missing from the official version since launch. I don't have any plans to adapt more patches, but may consider it if there's adequate demand.