MZ Companion v1.0: ask and build your RPG Maker MZ database with a free local model
Current Version (Video Tutorial Dropping in Link Above)–
MZ Companion is a small, always-on-top chat window that authors your RPG Maker MZ database for you — powered by a local, free Ollama model. Nothing leaves your machine, and there’s no API bill.
It works in two modes. Ask answers questions about your actual project — “what does skill #12 do?”, “list every fire item with ids,” or a full plain-English breakdown of every editor field on any entry. Build creates new entries and edits existing ones, then writes them straight into your data files: “add 5 health-regen items and a Regen state,” or “set Liquid Fire’s success rate to 50%.”
What it authors
items · weapons · armors · skills · enemies · actors · states
Ask by intent and it grounds the result in what you already have — “a fire weapon consistent with my existing ones” pulls your real assets and naming conventions, not generic filler.
Builder companion that actually understands your project
Create or modify. Brand-new entries, or in-place edits to existing ones — with a clear before→after diff on every change.
Standard target rules, enforced. Offensive items and skills (damage, drain, ailments) target enemies; healing and buffs target allies. If a scope contradicts the content, Build corrects it and tells you why — so a “damage item thrown at an enemy” never lands on your own party. Context-aware editing. “Rework item #39,” “change Searing Ember,” “make it cheaper,” even a correction like “I said #39” all resolve to the right entry. Too vague to act on? It asks instead of inventing something unrelated.
Knowledge & Artifacts
Knowledge grounds everything both modes do: drop in your lore, naming rules, and design docs (.md/.txt), plus an auto-index of your database and a glossary mapping your terms to real data. Semantic retrieval runs on a local embedding model (nomic-embed-text) when available, with keyword search as a fallback.
Artifacts save every Build plan under your project so it survives restarts — reopen one to review, re-apply, rename, or delete it, and applied artifacts are marked so you can see what’s already in.
Everything persists under
Safety net
Nothing is written until you click Apply. Every apply backs up the affected data/*.json files first, and Undo last restores the most recent backup. There’s also a 📷 button that snapshots the chat to your clipboard and saves a PNG — handy for bug reports and Discord.
The part that makes it reliable
Small local models can’t be trusted to hand-write RPG Maker JSON — one bad field corrupts a data file. So the model never writes JSON directly. It returns a small, constrained plan; the app merges that onto known-valid MZ templates, resolves names to the correct numeric IDs against your project (so “apply the Regen state” becomes the real ID even when Regen is being created in the same batch), validates, previews — and only then writes. That’s why the output always loads in the editor and stays consistent with what’s already there.
What’s next
Database authoring is the foundation. Coming next: maps, events, common events, and tilesets — and after that, both halves unified into a single Ask/Build surface.
Grab it above. You’ll need Node.js and Ollama, both free — the full one-time setup is in the README. Point it at a project, ask it what’s in your database, then tell it what to build.
Lastly, if you have any questions, suggestions, or find bugs please email me at within the companion “rpgmakerplugins@protonmail.com” so I can try to fix & address the community better. (I added easy screenshot exactly for this)
Originally posted on itch.io. See it on RPG Maker Market →