Status
This site describes the finished engine. This page is the one place that shows the gap between that target and today. “Built” means the work is in the engine and tested; “planned” means it is designed in the plan named and not built. Where something is built on one platform only, or was never run, the row says so.
Engine
Section titled “Engine”| Area | Built | Planned |
|---|---|---|
| Platforms | Desktop on Linux; DS ROM in melonDS; both from the same input logs with equal logs and pictures | Windows and macOS observed (plan 13); real DS hardware is not a target |
| 3D field | Maps of pieces on a grid of cells, heights to 31½ levels, ramps and bridges, stairs, hiding behind things; one world of maps with zones, streamed as you walk with no fade; warp kinds (doors, stairs, holes, panels and more); map variants by flag or variable; furniture cells; the location banner and signs; weather (ten kinds); a following creature; field moves and getting about (bicycle, surfing, diving); fishing | Seasons, moving map parts, more kinds of forced movement, reflections in the 3D field, rails and big cities, a map with its own gravity and camera rules (plan 25 steps 3 to 5; plan 20) |
| Cameras | Presets, camera zones on a map, cameras moved by script, each imported game’s own camera table | Generation 5’s moving and blended cameras as a style (plan 20) |
| Light and look | 14 light periods a day; light tables as data (lights.toml); the DS’s four hardware lights and material colours per period; edge marking and anti-aliasing as the DS draws them; fog; shadows that change by the hour |
One light model for every renderer (plan 42, 42c and 42d) |
| Tile-map field | GBA-style maps of tiles and metatiles drawn by the DS’s 2D hardware, running the same scripts, menus, battles and saves as the 3D field; 256-colour tile layers; picture tilesets; reflections and shadows | Game Boy-era maps as a mode (plan 35) |
| Scripts | A small language compiled to bytecode: procedures, arrays, text values, data queries, menus built by script, a game’s own commands named; 20 hooks (load, enter, talk, sight, steps, option, new game, resume, idle, the editing hooks and more); 4,096 flags | A game’s own Rust commands on DS (plan 46, after plan 36); script screens and declared saved records (plan 46) |
| Battle rules | Singles complete against Showdown (818 of 822 moves, 279 of 310 abilities, 264 held items); doubles, multi, tag and wild doubles; Mega Evolution; Terastallization; five trainer AI levels | Z-Moves and Dynamax (plan 36); triples (prepared, not written); rotation (needs the owner: Showdown has no reference) |
| Battle screen | Scenes and platforms as pictures by battle ground; the interface from a game’s own pictures; doubles on screen; battler motion as data; Black’s battlers as puppets; move animations as scripts with fallbacks | A 3D battle scene and moving camera (plan 25, B6); transitions by table (plan 25, B3) |
| A game’s own battle mechanics | Effects and overrides in a game’s Rust crate, reported by the build and run by the crate’s own host tests | The crate linked into the game’s desktop program and DS ROM (plan 46); ploom test --official and creator scenario tests (plan 34) |
| Menus and screens | Party, summary, bag, shop, storage boxes, naming, journal, trainer card, dex, options, region map, title and intro; built-in styles from Platinum (party, summary, bag, signs) and Emerald (Start menu, party), each a layout record a project can edit | One UI model for every screen (plan 45); the gadget framework: a device as a shell and apps (plan 45); region map zoom and fly (plan 21) |
| Lower screen | A picture, the menu as touch buttons, or a few small apps ([ui.bottom]) |
Gadgets registered by script, the C-Gear imported as one (plan 45) |
| Game systems | A sectioned save, one folder per game; the clock, daily and weekly resets; evolution (every Essentials method); day care, eggs and hatching; roamers and the lead’s effects on the wild roll; move relearner, tutors, deleter, name rater; Hall of Fame and credits; challenge mode with permadeath; currencies; rules, options and cheats | The built-ins of plan 46 (visible encounters, level scaling, quests, portraits, outfits, save slots); contests, the minigame host and battle facilities (plan 25 step 5) |
| Audio | Tracker modules (Maxmod on DS, a Rust player on desktop); effects loaded on demand; cries; music rules by place, time and travel; interface sounds as data; stereo or mono | Interactive music layers (plan 25, A2). Desktop sound through a device: never heard |
| Presentation | Presentation settings in their own crate, with presets, a device file and a game’s caps; the replay proof that they change nothing; colour-vision filters, less motion, less flashing; the wide 320×180 desktop canvas | Resolution scale and post-processing in the software renderer, a wgpu desktop renderer with shadow maps, water and ray tracing (plan 42); the other quality-of-life rows (plan 44) |
| Multiplayer | A link battle between two desktops (pl-net, a relay server); up to 8 players in one world with two local inputs on one machine |
Trades, rooms, friends, gifts, the online server’s features (plan 33); online co-op and split screen (plan 43, decision 321) |
| Creator kit | ploom new, build, build desktop, check (with --art), schema, run with live reload, tiles, pack, fetch-data, fetch-pbs, fetch-sprites, fetch-trainers, sync, sheet, battle-pic, fit, import, assets, catalogue, source, restyle |
ploom build nds without the DS toolchain and a release with prebuilt runtimes (plan 13, plan 26); ploom test (plan 34); ploom add for packages (plan 46); a debug overlay; the editor (plan 38) |
| Importer | Platinum, HeartGold and Black from ROMs; Emerald from its decompilation; Black 2’s text and C-Gear; assets organized by role; one game drawn in another’s art | Black 2’s maps and scripts; every other game before the 3DS (plan 35, not scheduled); Essentials games (plan 23, waiting) |
| Testing | Host tests; test-nds sessions on desktop and melonDS; golden images; the Showdown fuzzer; the pairs tool against the real games; results cached by their inputs |
CI’s first run on its remote host observed; mGBA in the pairs tool for Emerald |
Imports
Section titled “Imports”| Game | From | Plays today |
|---|---|---|
| Platinum | ROM | Its opening through the first wild battle; the first town to the first route can be walked |
| HeartGold | ROM | From the bedroom through the starter to a won wild battle, desktop and DS agreeing |
| Black | ROM | The bedroom’s scene to the first battle, on desktop |
| Emerald | Decompilation | From its opening through the starter to the first battle, on desktop and DS |
| Black 2 | ROM | Text and the C-Gear only; its maps and scripts are not imported yet |
Budgets
Section titled “Budgets”The DS’s 4 MB of RAM is split into budgets (plan 00). The heap figures are
cargo xtask profile-nds over every map of the demo game (demo/); the code size is
cargo xtask size. They are the last reported numbers, not measured for this page.
| Budget | Limit | Last measured |
|---|---|---|
| ARM9 code and static data | 1,572,864 bytes (1.5 MB) | 1,030,304 bytes, 65.5 % |
| World heap | 512 KB | 123,101 bytes peak |
| Battle heap | 256 KB | 116,892 bytes peak |
| Asset staging | 512 KB | 169,276 bytes peak |
| Audio (music 320 KB of it) | 512 KB | 85,488 bytes for the sample; imported games peak at 85 to 88 % of sound memory |
| Stack | about 15 KB | deepest mark 11,016 bytes |
| Polygons a frame | 2,048 (the hardware’s) | 214 in the demo |
| Frame time | one 60 Hz frame | worst steady tick 40 % (the demo) |
Code size is the largest risk: it rose from about 40 % to about 65 % of its budget as the battle content, the interface styles and the systems above landed. The gimmicks still to come (Z-Moves, Dynamax) and the field’s later features must fit in what is left. Plan 09 names two relief valves: code overlays, and battle effects loaded per battle. Neither is built.
Not measured for imported games yet: the heap and polygon figures above come from the demo, not from an imported Platinum, whose views needed 256 meshes (decision 194).
Milestones
Section titled “Milestones”| Milestone | State |
|---|---|
| M1 Walk the town | Done |
| M2 Battle on the command line | Done |
| M3 Grass to battle | Done |
| M4 Game loop: party, bag, trainers, saving, healing, shops | Done |
| M5 Full modern content: every effect and all four gimmicks | Singles, doubles, Mega Evolution and Terastallization done; Z-Moves and Dynamax to do |
M6 Creator kit: ploom new to a .nds with no Rust |
Not done: the ROM still needs the DS toolchain |
The work that follows is on the Roadmap.