I love RPG Maker. I’ve loved it long before I first used it and was extremely jealous of the American PS1 owners who got to use it on console, and I was thrilled when I first discovered the legendary unofficial localisation of RPG Maker 2000 by Don Miguel. The game I made with moral support from my friends at university, The Adventures of Dave Thunder, was shaping up to be a lot of silly fun — albeit probably far too full of in-jokes to be appreciated by anyone outside my circle of friends — but it was unfortunately lost when my computer at the time suffered a catastrophic system failure. I’ve never quite forgiven myself for not backing it up.

But I’ve maintained an interest in RPG Maker ever since, and have fiddled around with numerous incarnations over the years. Most recently, I snagged a copy of RPG Maker MV, the latest version, in the recent Steam sale, and I’ve been having a play with it. It seems like a lot of fun so far, and a good evolution even from VX Ace, the previous edition.

The basic toolset is almost identical. There’s a simple tile-based map editor for you to draw your various locations using tilesets — either those included or those you create yourself in an external art program. On top of that is the Event system, which allows you to place objects and triggers on your map and, constructing pseudo-code through a menu-driven interface, make them do all manner of different things, ranging from being a random NPC wandering around spouting bollocks to a lengthy cutscene event that changes depending on your previous actions in the game.

The basic Event system is very powerful and flexible, but for the last few versions of RPG Maker it’s also been supported by the ability to use scripting — actual coding — alongside the pseudo-code created in the Event editor. Previously, RPG Maker used a variation on Ruby for its scripting language; in MV, it’s made the change to straight JavaScript, arguably a much more widespread (and easier to learn?) language.

What’s particularly nice about MV’s scripting support is that it’s organised in a completely different way to previous incarnations. Instead of having a huge, daunting Script Editor window where it’s possible to completely break your whole game with just one little typo, RPG Maker MV works by using JavaScript plugins. Drop these in the appropriate subfolder of your project, activate them within RPG Maker, configure them as appropriate, then off you go.

It’s a simple change, but a very effective one. The fact that each plugin is treated as its own module with its own settings means that plugin creators can create a simple list of parameters that less code-savvy RPG makers can tweak and change without having to even look at any JavaScript whatsoever. Many plugins also have “friendly”, easily readable Plugin Commands to trigger various functionality, too — no more “this.enemyType(math.random(floor.bollocks));” or whatever, although you still can perform direct script calls if you so desire.

Best of all, the localisers Degica have embraced the most active members of the RPG Maker community over the years and brought them on board to help out with making RPG Maker MV an excellent package. Legendary RPG Maker scripter Yanfly, for example, has produced a huge number of plugins for MV already, and other well-known contributors to the community such as Archeia have played an important and active role in making RPG Maker MV what looks like the definitive version of RPG Maker… until the next one comes out, of course.

I’m just farting around with it at the moment with no real grand plan in mind; I’m putting together a relatively straightforward game using mostly standard assets as a means of getting my “eye” back in as well as learning MV’s new features. It’s not going to be anything amazing or revolutionary — going by previous experience, it probably won’t be finished, either — but it’s providing something fun to do when I want to keep my mind occupied.