Phase 33 adds a bounded, non-executable Ruby Marshal 4.8 structural parser/serializer for verified RPG Maker XP, VX, and VX Ace workflows. It preserves supported object and symbol references and does not evaluate Ruby code. Only fields whose class and instance-variable shape is fixture-backed are exposed for editing; everything else remains preserved or rejected fail-closed.
RPG Maker Tools
RPG Maker Database Viewer
Inspect bounded RPG::* class counts and a safe structural preview in XP/VX/VX Ace Ruby Marshal project data.
01 / Tool workbench
Use the runtime only when it is actually ready.
The application shell fails closed. An input interface is not enabled merely because a WordPress Tool record exists; the declared engine must be registered in the current build.
Session change summary
No output has been built in this session.
02 / Compatibility
Know the supported input before opening a file.
Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.
Accepted extensions
.rxdata.rvdata.rvdata2
Platforms
RPG Maker
Supported versions / editions
Fixture-backed RPG Maker XP .rxdata, VX .rvdata, and VX Ace .rvdata2 files using Ruby Marshal 4.8 and standard RGSS-style class/instance-variable shapes. Custom scripts can change object layouts and remain unsupported unless the required shape is proven.
Input constraints
Local input is capped at 4 MiB. Ruby Marshal parsing is bounded by stream, object, collection, depth, and byte-sequence limits. Unsupported type bytes, malformed reference tables, missing expected classes, or ambiguous layouts fail closed. RPG Maker 2000/2003 .lsd is a separate unsupported binary family.
Known limitations
Read-only structural inspection. The viewer does not execute Ruby objects, scripts, custom marshal callbacks, or project logic.
Output / result
A read-only class summary and bounded preview; no edited file is generated.
03 / Instructions
Use a reversible workflow.
File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.
- 01Keep the original
Preserve an untouched copy before creating or transforming binary output.
- 02Confirm scope
Match the file size, format, platform, and version to the support information on this page.
- 03Process locally
Use the runtime only when the page reports that its declared engine is loaded.
- 04Validate output
Compare or test the result before replacing any working source file.
Tool-specific steps
Open a supported project-data file and review the detected RPG::* class counts and safe preview.
04 / Privacy and processing
The processing mode is part of the product contract.
SaveEditor.com should state local processing only when the implementation truly keeps file contents in the browser. Server or hybrid processing must be disclosed just as clearly.
Declared mode
Browser local
Runtime state
Operational
Tool-specific privacy notes
Phase 33 reads the selected file only after explicit local file selection. Standard MV/MZ processing and bounded XP/VX/VX Ace Ruby Marshal parsing, supported edits, validation, and export run in the browser. The RPG Maker runtime contains no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. Selected files are capped at 4 MiB; unsupported or ambiguous legacy structures fail closed.
05 / Troubleshooting
When a file is rejected, do not force it.
A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.
Re-check the documented input type and browser size limit before retrying.
A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.
Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.
Known Tool issues
Unsupported Marshal constructs or malformed reference graphs are rejected.
06 / Verification
Support claims should be traceable.
The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.
Last verified2026-08-08
Profilerpg-maker-database-viewer
Method notes
Verified with synthetic Ruby-generated XP/VX/VX Ace fixtures, byte-identical no-edit round trips, bounded malformed-input rejection, JavaScript structured-edit round trips, and Ruby re-load interoperability of JavaScript-generated outputs.
Public references
- https://github.com/rpgtkoolmv/corescript
- https://github.com/leandiez/rmmz-corescript-dev/blob/master/src/rmmz_managers/StorageManager.js
- https://github.com/altivi/lz_string
- https://github.com/Maruno17/pokemon-essentials/blob/master/Data/Scripts/002_Save%20data/001_SaveData.rb
- https://ruby-doc.org/3.4.1/stdlibs/marshal/marshal_format.html
07 / FAQ
Questions to answer before editing.
These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.
Is RPG Maker Database Viewer ready to use?
The Tool record is verified and declares an operational runtime. The page enables its input controls only when the declared engine module is loaded in the current build.
Does processing stay in the browser?
Yes for this declared mode. The loaded runtime processes the explicit input in the browser; Tool-specific privacy notes describe the exact scope and limits.
Should I keep the original file?
Yes. Keep an untouched source file until any generated output has been validated.
What if my input is rejected?
Use the validation message to correct the base, encoding, width, timezone, byte alignment, or size. The runtime does not guess through invalid input.
Related tools
Continue with the same tool family.
Only index-ready verified records from the same Tool Family are shown here.