# Port an RPG Maker game out of the default template > Porting an RPG Maker game means rebuilding a project you own. The database and maps convert as data. RTP assets cannot legally come with you. - URL: https://www.summerengine.com/port-an-rpg-maker-game - Keyword: port an rpg maker game - Related: https://www.summerengine.com/porting Porting an RPG Maker game means rebuilding a project you own in a general purpose engine. The reason people do this is usually not performance. It is that the RPG Maker event system, fixed grid, and battle framework stop matching what the game wants to be. One rule matters more than any other here. RTP assets, the runtime package art, music, and tiles that ship with RPG Maker, are licensed for use in RPG Maker products. They cannot be carried into another engine. Anything you made, commissioned, or bought under a general commercial license can move. Plan for replacing RTP content before you start. The rest is tractable. RPG Maker MV and MZ store their database as JSON files, so actors, classes, skills, items, enemies, and troops convert into your own data tables. Summer Engine rebuilds the maps, systems, and battle flow into a project you own, with no royalties, exportable as desktop builds for Steam and itch.io. ## The database converts as data, not as code RPG Maker MV and MZ keep the database in JSON under the data folder: Actors, Classes, Skills, Items, Weapons, Armors, Enemies, Troops, States, and more. Those files are readable and convert into resource files or tables in the rebuilt project. VX Ace uses rvdata2 archives and Ruby scripting, which are harder to read and usually get re-entered or exported through a script. Convert the data first, because it is the cheapest part of the port and it defines everything else. ## Events and switches become real code RPG Maker event pages with conditions, switches, variables, and self switches are a state machine expressed in a list editor. In a rebuild they become scripts, which is both the hard part and the reason to move. A dialogue event becomes a call into your dialogue system. A chest becomes an interaction node with an item reference. Hundreds of copies of the same event pattern collapse into one reusable scene, which usually shrinks the project dramatically. ## Maps, grids, and what you can change RPG Maker MV and MZ use 48x48 pixel tiles, and VX Ace uses 32x32, with a fixed tile grid and layered autotiles. A rebuilt project uses a tilemap that can keep the same grid exactly, so the maps feel identical if that is what you want. What you gain is optional: free movement instead of grid steps, diagonal movement, larger character sprites that overlap tiles, real lighting, and cameras that are not locked to the grid. ## The battle system is where the port pays off The default front view or side view turn based battle framework is the most common thing developers want to replace. Rebuilt, the battle system is yours: turn order, action timing, positioning, animations, and UI are all code you control. You can keep a faithful turn based system, add an active time bar, or move to something completely different. Plugins that patched the default system no longer apply, so list every plugin you depend on and decide what each one becomes. ## FAQ ### Can I use RPG Maker RTP assets in another engine? No. RTP art, music, and tiles are licensed for use in RPG Maker products. They cannot be shipped in a game built in another engine. Replace them with assets you created, commissioned, or licensed without an engine restriction before you ship. ### Can my RPG Maker database be converted automatically? Largely yes for MV and MZ. Those versions store the database as JSON files under the data folder, so actors, classes, skills, items, enemies, and troops convert into data tables in the new project. VX Ace uses rvdata2 archives, which usually require an export script or manual re-entry. ### What happens to my events and plugins? Event pages become scripts, which is the main work of the port. Repeated event patterns collapse into a single reusable scene. Plugins do not transfer, so list every plugin the game depends on and decide whether each becomes rebuilt code, a different approach, or a cut feature. ### Do I have to give up the tile grid? No. A rebuilt tilemap can keep the same 48x48 or 32x32 grid and the same map layouts. Free movement, diagonals, oversized sprites, real lighting, and unlocked cameras become available, but none of them are mandatory. ### Why port an RPG Maker game at all? Usually because the default battle system, the event system, or the grid limits the design. A rebuild makes the combat, UI, movement, and presentation your own code. It also gives you desktop builds for Steam and itch.io from one project you own with no royalties. [Rebuild your RPG Maker game](https://www.summerengine.com/download) --- ## Machine-readable resources - Site index for agents: https://www.summerengine.com/llms.txt - Full inlined content: https://www.summerengine.com/llms-full.txt - Porting catalog: https://www.summerengine.com/llms-porting.txt - Structured catalog: https://www.summerengine.com/agent-catalog.json - Sitemap: https://www.summerengine.com/sitemap.xml - Developer resources: https://www.summerengine.com/docs