Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

FF9 Map Kit (ff9mapkit)

Author custom Final Fantasy IX content (Steam/GOG, via the Memoria engine) from declarative TOML projects, compiled into drop-in Memoria mods. Part of the Dream World IX project.

Capabilities: author any field camera from scratch (single / scrolling / multi-camera) with a pixel-accurate paint guide · fork any of ~674 real fields — camera, walkmesh, art, exits, encounters, music, and (verbatim mode) the real script and dialogue · NPCs, dialogue choices, gateways, events, story branching, cutscenes, shops, save points from one field.toml · custom 3D battle backgrounds + battle tuning · multi-field campaigns and journeys · custom 3D character models (Blender round-trip) and playable characters · overworld terrain/coast/entrance authoring · custom music/SFX · save and story-state editing.

Authoring surfaces: TOML by hand, the form editor (ff9mapkit edit), the Blender add-on, and the one-window PySide6 Workspace.

What it does

Given a field.toml describing one field — camera, painted background layers, walkmesh, NPCs, dialogue, gateways, encounter, music — ff9mapkit build emits everything a custom field needs:

  • the background scene (.bgx/.bgs + overlay PNGs or atlas) and walkmesh (.bgi),
  • the field event script (.eb) for all seven languages,
  • dialogue text (.mes),
  • the DictionaryPatch / BattlePatch registration + ModDescription.xml.

Battle maps (battle.toml), campaigns (campaign.toml), and journeys (journeys.toml) compile the same way at their own scopes.

Two steps stay manual, matching how the original pre-rendered backgrounds were made: painting the background art (over the kit's projected paint guide) and judging final in-game alignment. The pipeline rationale is in docs/PIPELINE.md.

Quickstart

pip install "ff9mapkit[assets]"                  # or from this dir: pip install -e ".[assets]"
ff9mapkit setup                                  # find the FF9 install, extract base assets
ff9mapkit import <field> --out myroom --verbatim # fork a real field — or `new` for original art

Full setup (extras, game-path resolution, the engine bundle) → SETUP.md. First-time walkthroughs → docs/tutorials/.

Commands

114 subcommands — ff9mapkit -h lists them; the grouped reference with flags is in SETUP.md §7. The families:

  • Setup — setup · doctor · extract-templates
  • Author — new · guide / paint-template · walkmesh · edit · camera · disasm
  • Build & ship — build · lint · pack · export-art · repaint-native
  • Fork real fields — import (--editable/--native/--verbatim) · import-all · import-chain · fork-report · list-fields / find-field / find-rooms · logic-map / lint-eb
  • Campaigns & journeys — new-campaign / add-field / build-all / lint-campaign · gen-hub / lint-journey / assemble-journey / reference-arcs · deploy-campaign / deploy-journey / newgame
  • Battle — battle-import / battle-build · battle-list / battle-scene / battle-ai / battle-seq · battle-patch / characters / ability-gems / ability-features
  • 3D models — model-gltf / model-import / model-mint / model-anim / model-export / playable-anims
  • Overworld — world-terrain / world-reclaim / world-coast / world-transplant / world-water / world-island / world-forest / world-hill / world-mountain / world-entrance / world-encounters and the rest of the world-* suite
  • Audio — audio-import · music-list / sfx-list
  • Catalogs & dialogue — catalog / models / animations / archetypes / items / scenes / flags / sps · dialogue / dialogue-import
  • Saves — flags-inspect / flags-diff / save-edit · items-inspect / items-set-*

Docs

Validation

The package is organized by domain: eb (event-script codec + content injectors), scene (camera math, .bgx/.bgs, .bgi walkmesh, paint guides), build (the field.toml compiler), plus battle/, world/, models/, content/, deploy/journey orchestration, and the editor/+workspace/ front-ends.

Correctness is proven offline by a golden-master test suite (~2,850 tests): every codec round-trips real install assets byte-for-byte (regenerated locally via extract-templates — the repo ships none), and compiling the bundled examples reproduces in-game-verified output exactly.

pip install -e ".[dev]"
py -m pytest -n 6

Metadata

Release files for ff9mapkit 1.0.0b17

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ff9mapkit 1.0.0b17
File Size Uploaded
ff9mapkit-1.0.0b17.tar.gz 3.1 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for ff9mapkit 1.0.0b17
File Interpreter ABI Platform
ff9mapkit-1.0.0b17-py3-none-any.whl Python 3 none any Details

Total release size: 5.6 MB

Release files / ff9mapkit-1.0.0b17.tar.gz

Download URL ff9mapkit-1.0.0b17.tar.gz
Size 3.1 MB
Tags Source
SHA-256 checksum
How to use checksums
714bdf7b59817e6c2df359d3c69cb1d10935b9e488b735dffbe9cd4fd3d2c5b8
BLAKE2b-256 checksum
How to use checksums
7be52013e714912900451be470afd8f0f0f9f8776f42cbed2b5ba60ae3b4468d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 19, 2026.

Transparency log

Release files / ff9mapkit-1.0.0b17-py3-none-any.whl

Download URL ff9mapkit-1.0.0b17-py3-none-any.whl
Size 2.5 MB
Tags Python 3
SHA-256 checksum
How to use checksums
4369250e2ccc48537a6f298a5801fe52ab931fd60b7da31bab4a0a810851a12c
BLAKE2b-256 checksum
How to use checksums
8f6ee9af9d4ba1776a21cf7a7e13a218d09474d010929cb4c5bafd2605e17b4e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 19, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page