RPG Maker event viewer FAQ

Open MakerLens Events, press Select Game Folder and pick the game's folder, or drop the folder anywhere on the page. Pick a map in the sidebar, then an event: its commands appear as a flow graph. Click a node to read its full text in the side panel, and use the page tabs for events with more than one page.

The game's root folder works, and so does its data/ folder on its own. MV games keep it in www/data/, MZ games in data/; MakerLens Events finds either. It reads MapInfos.json (the map tree), every Map###.json, CommonEvents.json, System.json (switch and variable names) and Actors.json. Images and audio are not needed.

No. It reads a released game as it is shipped, so you don't need to own RPG Maker, open the project or start a playtest. That is the difference from node editors and debugger plugins, which run inside the game or the editor. Nothing is installed into the game, and the game is never changed.

RPG Maker MV and MZ, whose event data is plain JSON. XP, VX and VX Ace store events in Ruby files (.rxdata, .rvdata, .rvdata2) and are not supported yet, nor are RPG Maker 2000 / 2003. For the images and audio of XP, VX and VX Ace games, use MakerLens Assets.

It found no data/ folder and no Map###.json file in what you selected. Select the game's root folder (the one with Game.exe) or its data/ folder, not img/ or audio/. Some released games pack all their files into the .exe or encrypt data/ with a plugin; MakerLens Events cannot read those.

Five kinds of node: dialogue (Show Text, with the speaker name in MZ), choices (Show Choices, one branch per option), conditions (Conditional Branch, with its Else branch), labels, and jumps to a label, drawn as dashed arrows. Other commands, such as Control Switches, Transfer Player, a Common Event call or a script, are not drawn yet.

Open the event that starts the ending and follow its condition nodes: each one names the switch, variable or actor it tests, such as If [Switch: Met the witch]. Then look for the event that leads into that branch. Note that the conditions on an event page's own settings (the editor's page conditions) are not shown yet; switch between the page tabs to compare pages.

Yes. Names come from the game's System.json and Actors.json, so a condition reads If [Variable: Gold found] rather than a bare number. In dialogue, the \N[n] and \V[n] text codes are replaced with the actor name and the variable name. A switch without a name shows its number instead, such as If [Switch #12].

Yes. Common events are listed below the maps in the sidebar and open as graphs the same way. Maps keep the tree and folder order of the editor, from MapInfos.json.

Yes. Scenes, the common events and event pages that show pictures together with dialogue, are listed under Scenes at the top of the sidebar, and the Preview button plays the page on screen. The player dims the page and shows the scene at the game's screen size, line by line, with its pictures, picture animations, face graphics, music and sound effects. Messages type themselves out at an reading speed of 300 words a minute (T or the T button shows whole lines instead); click or press → to continue, ← to go back, A for auto play, which leaves each line on screen for two more seconds once it is shown in full; choices are offered as buttons. At the end of a scene the next one in the Scenes list follows on, and going back from the first line opens the previous one (Shift+→ and Shift+← skip a whole scene). H or the eye button hides the dialogue so you can see the pictures; a click brings it back. When a picture depends on the hero's state, such as the outfit they wear, the player shows the game's starting state. Open the game's root folder (not data/) so the pictures and audio can be found: encrypted files are decrypted in memory, never saved or uploaded. Simple scripts that show or erase pictures or set variables are followed; other effects made by plugins or scripts are not played.

Find the line's dialogue node and follow the arrows back up: the choice option or the If / Else branch above it is the branch. Click any node to read the full text in the side panel. This is handy for translators who need to know when a line is said.

No. MakerLens Events is read-only: it never writes to the game files and has no export. To change events, use the RPG Maker editor. You can drag nodes to tidy the graph (with undo and redo), but that only changes what you see.

No. Files are read by your browser and never leave your device. The page's Content-Security-Policy blocks requests to any server except an anonymous page-view counter, which receives only the page address and referrer, and the optional feedback form, which sends only the rating and comment you choose to send. Details: Privacy & analytics.

No installation and no account. It works best in Chrome or Edge; Firefox works too, through its folder picker. All libraries are served from this site, so once the page has loaded it works without an internet connection. The source code is on GitHub (MIT license).

MakerLens Events only reads files that are already on your computer and changes nothing. It is meant for your own games, or games you have permission to study, for example to write a guide or a translation. Reusing a game's story or text elsewhere may need the rights holder's permission, so check the game's terms.

Use MakerLens Assets, the other MakerLens tool. It opens the same game folder and previews and downloads its encrypted images and audio (.rpgmvp, .png_, .ogg_ and more), also in your browser.