Rpg Maker Developers Group

Everything is based on event templates. The first thing you need to do is create a few maps to serve as a template sheet. You can create any number of maps you want, and even give them names, which you can later use to load your event templates!

On each of your map templates, create and organize the events you need. As with maps, events can be given a name, which can be used to reference it later. Just make sure that the combination of "Map Name" and "Event Name" are unique, otherwise we may run into trouble later. Then open the Plugin Manager and fill the only plugin parameters displayed with the map IDs from your template maps.

After that, just use note tags and plugin commands to reference one of your templates.

Be careful though: transforming an event into another do not alter the self switches states. So if the event's self switch A is on, for example, transforming it into another event won't change that. The event ID and Name are also not changed (so you can still reference them in move route commands, for example).

Also, event transformations are automatically saved and load any time the event is loaded again. That means that going out and back from the current map won't reset the transformation. The only way to do that is through explicit plugin commands.

WARNING: Map and event names cannot contain either the , or > symbols. If you're an MV user, I'd advise against creating names containing blank spaces, as that will make them unreachable through plugin commands.
If you're using MZ blank spaces are not a problem (, and > are still a no no though).

Setting a note tag in an event will cause it to automatically transform into the referenced template the first time it is loaded (as long as the map and event keys provided exists within our templates).

The basic note tag is as follows:
mapKey can be either the map template ID or its name. The same applies to eventKey (event ID or event name). Keep in mind that if you choose to reference them by name their name is case sensitive and the combination of both must be unique for this to work properly.

Remember: self switch states won't change when an event is transformed. When talking about note tags, that means that an event will always load with all self switches turned off, at least initially. But what if, for some reason, we want it to turn one of them on by default?
That can also be done with note tags:
sw:abcd means that all four self switches will be turned on by default. If you don't want all, but just one of them to be turned on, just list it and not the others. For example:
here we're loading event1 from map1 with self switch A already on.
and here we're loading the same event, but with switches C and D turned on.

$gameSystem.getMapIdByName(mapName)

$gameSystem.hasEventTemplateData(mapId, eventId)

$gameSystem.deleteEventTemplatesData(mapId, eventId)

$gameSystem.transformLocalEvent(eventId, mapKey, eventKey, noHistory)

$gameSystem.transformRemoteEvent(mapId, eventID, mapKey, eventKey, noHistory)

$gameSystem.rollbackLocalEvent(eventId, n)

$gameSystem.rollbackRemoteEvent(mapId, eventId, n)

$gameSystem.resetLocalEvent(eventId)

$gameSystem.resetRemoteEvent(mapId, eventId)

Transform Local Event

Transform Remote Event

Rollback Local Event

Rollback Remote Event

Reset Local Event

Reset Remote Event