This script replaces the way common events are created and managed. Instead of using the database to set up common events, you create a special “common event map” and all events on that map will be loaded as common events.
The advantage of using these extended common events include having multiple pages for a single common event and setting up complex common events using conditions.
These extended common events will replace the database common events, but you can still use the database common events to set the names so that you can reference them throughout your project.
Script: download here
In the script editor, place this script below Materials and above Main.
You should place this above other custom scripts.
Create a map for your common events, and then in the configuration set up
the filename of this common event map. Note that you don’t have to use an
actual map in your current project: you can choose any name you want as long
as it is a map file. This means you can create the common event map in a
By default, each event created on the map will be loaded as a common event
based on its ID. So for example, if the event’s ID is 12, then it will replace
common event 12 in the database.
You can choose which common event an event will replace manually by writing
the following as its name:
<common event: x>
Where x is the common event ID. This allows you to replace specific common