Add code or a plugin
Use the official instructions, then test one small feature before changing the rest.
- STEP 1
Back up your licensed project
Use an authorized MZ copy and a backup of one small test project. Record the actual editor and project core versions. Confirm your purchase eligibility and the separate plugin licence before adding files.
Check: Your backup and versions are recorded; no live project has been overwritten or new purchase assumed.
- STEP 2
Enable a compatible plugin
Choose an MZ-specific plugin with its own documented installation and rights. In Tools → Plugin Manager, enable it and set its parameters. Official new-project plugins and separately supplied DLC are different sources. MV plugins, generic JavaScript and npm packages are not automatically MZ-compatible.
Check: The intended MZ plugin is enabled once and its required parameters are recorded.
- STEP 3
Try one event before expanding
Use the enabled plugin’s Plugin Command and documented arguments, or a small Event Script using your own code. Run Game → Playtest and inspect F8 developer tools. Keep licensed vendor files and assets out of AI uploads unless their exact terms permit that use.
Check: You observed the intended event result and checked actual errors; an absent error alone is not proof of correct behaviour.
- STEP 4
Check the deployed files separately
Test the Windows, macOS or web deployment you actually need. Web output needs an HTTP server and supported browser features. Exclude unused files can miss plugin-referenced assets; inspect those files and the documented MaterialBase plugin. Keep required notices. Encryption does not guarantee prevention of copying.
Check: The target build contains required assets and works in your actual target environment. Native mobile, physical-device and export success remain unverified by Forge.
Limits & official instructions
- An engine-specific plugin cannot usually be pasted into a different engine.
- Downloaded code and setup scripts can run with your machine’s permissions; review and isolate first.
- Keep the official licence/notice files and check any dependency-specific terms.
Tools and Plugin Manager · official MZ manual ↗
Event Script and Plugin Command · official MZ manual ↗