Settings
A PokeLoom game looks like a DS game because the engine draws it by the DS’s rules. On a desktop a player may want more: a sharper picture, smoother edges, soft shadows, glowing lamps. The engine allows that, under one rule that is never bent: a presentation setting changes only pixels. It never changes the game’s state, its random numbers, the input log, a save, a script’s run or the sounds it asks for. A game may look different on desktop and DS; it never plays differently (decision 310). Why that rule holds, and how it is proved, is on Presentation and game state.
Each setting is a row: a name, its choices from least to most, and how the DS
draws it. Rows are named by what they do (bloom, reflections, resolution), never
by a game or a renderer’s internals.
Every row declares its DS class:
| Class | Meaning | Examples |
|---|---|---|
native |
the DS draws the same idea with its own hardware | anti-aliasing, fog, outlines, 30 or 60 frames a second |
approx |
the DS draws a cheaper form | shadows, reflections of characters only, colour filters |
off |
not drawn on the DS; the DS’s options hide the row | resolution, bloom, upscalers, depth of field |
The rows of the graphics table, from plan 42:
| Row | Choices | On the DS |
|---|---|---|
renderer |
exact (the software renderer), gpu |
the hardware |
resolution |
1× to 4×, fit |
1× |
antialias |
ds, fxaa, ssaa2, ssaa4, msaa4, msaa4-fxaa |
the game’s own anti-aliasing |
upscaler |
nearest, sharp-bilinear, xbrz, scalefx, lcd, crt |
none |
textures |
nearest, bilinear, upscaled |
nearest |
frame_rate |
30, 60, display |
30, or 60 where a map’s budget allows |
particles |
×1 to ×4 | the game’s counts |
draw_distance |
×1 to ×3 | the game’s |
widescreen |
4:3, 16:9, 21:9 | 4:3 |
fog |
ds, smooth, height |
the DS’s fog table |
outlines |
off, ds, scaled |
the map’s outlines |
shadows |
blob, shadow maps of 512 to 4096, soft, traced |
blob shadows by the hour |
cloud_shadows |
off, game, layer, projected |
a scrolling layer, or off |
reflections |
off, characters, scene, screen, traced |
characters only, or off |
water |
ds, modern |
the game’s water |
lighting |
ds, pixel, lamps, bounce |
the period’s light |
bloom |
off, low, high |
none |
grading |
ds, lut |
the period’s tint and the map’s grade |
ambient_occlusion |
off, ssao, traced |
none |
depth_of_field |
off, cutscenes, always |
none |
motion_blur |
off, afterimage, object |
an afterimage, or off |
toon |
the game’s | the DS’s toon table |
Then come the accessibility rows (colour_vision, high_contrast, less_motion,
less_flashing, hud, text_size); they are on
Accessibility and quality of life.
A preset sets every graphics row at once:
| Preset | Meaning |
|---|---|
classic |
the DS’s picture. The DS comparisons and the fidelity pairs use it. |
high |
a modern picture for an ordinary machine |
ultra |
everything the machine can do |
auto |
what this machine can hold, measured |
Changing a row after choosing a preset shows custom. Presets never touch the
accessibility rows.
What is drawn today
Section titled “What is drawn today”The table above is the design. Today the desktop draws with the software renderer at
the DS’s own resolution, so every preset shows the classic picture except for the
rows that are drawn: the colour-vision filters, less motion and less flashing. A row
that does nothing yet is accepted and named as such on the program’s error output.
auto comes to classic until the GPU renderer and its detection exist.
Storage
Section titled “Storage”Presentation settings are a property of the device, not the game:
| Platform | Where | Never in |
|---|---|---|
| Desktop | the desktop’s config file, as name = value lines beside the window settings; one file shared by every game |
the save, the pack, the input log |
| DS | fat:/ploom-device.cfg beside the save slots, the same text; on a card with no file system the defaults are used |
the save |
preset = high # classic, high, ultra or autobloom = low # any row, after the presetKeeping them out of the save is part of the proof: a save written at any preset is
the same, byte for byte. On desktop every row can also be given on the command line,
--preset ultra and --set bloom=low, which is how the headless runner and the proof
use them.
A DS is a fixed device: it starts at the DS’s values, and only its own few rows can be changed, to the DS’s choices.
Planned (plan 42): a Graphics page in the options screen, on desktop with every row
and on the DS with only its native and approx rows, and auto that picks a preset
from the graphics card and then times the first seconds of play, stepping down until
frames keep up.
Creator settings
Section titled “Creator settings”A game states its look decisions in [graphics] in game.toml:
[graphics]default = "classic" # the preset a new player starts at; auto without itmodern = true # false: only classic, and the upscaler and accessibility rowscap = { bloom = "low", shadows = "map-2048" } # the most a player may choose of a rowA new player starts at the game’s default, or at auto when the game sets none. A
creator who wants the DS look kept can set modern = false. Caps bind the player,
because the look is the creator’s art decision, with one exception: accessibility
rows can never be capped (decision 315); the build refuses such a cap. Every key is
in the game.toml reference.
Renderers
Section titled “Renderers”The software renderer, the reference
Section titled “The software renderer, the reference”The desktop draws the 3D field with soft3d, a software renderer that follows the
DS’s rasterization rules: the same edges, the same fixed-point maths, the same 5-bit
colour, the same lighting sum, fog table, outlines and anti-aliasing. Its picture is
compared with melonDS’s on every 3D test session and must agree on all but 1 % of 3D
pixels; 2D must be equal. It stays the reference that every other path is measured
against. See Rendering.
Planned (plan 42): above 1×, a scaled copy of the same rasterizer draws more pixels with the same rules, and the 2D layers are composed over it at a whole scale so pixel art stays crisp. A post-processing chain then adds anti-aliasing, bloom from emissive materials, colour grading by period or map, the colour-vision filter and the 2D upscaler, in a fixed order.
The GPU renderer
Section titled “The GPU renderer”Planned (plan 42): pl-gpu, a second desktop renderer on wgpu (Vulkan, Metal,
DirectX 12, OpenGL as a last resort). It reads the same scene description the DS draws
from, never the game. At classic it reproduces the DS’s rules in shaders and must
agree with soft3d on all but 2 % of 3D pixels. Then each effect is a pass that reads
only the scene and the settings:
- shadow maps from the period’s sun, with characters’ cards alpha-tested;
- modern water with a mirrored reflection, refraction and Fresnel;
- lamps as point lights at the lamp materials;
- bloom, grading and anti-aliasing in shaders;
- ambient occlusion and depth of field in cutscenes;
- ray-traced shadows, reflections and one bounce of light.
It is desktop only and never linked into the DS build. Without a graphics card, or if
the device is lost, the game falls back to soft3d for the run.
One light model first
Section titled “One light model first”Today the engine lights a map in one of two ways, palettes tinted by the period or the DS’s hardware lights, and they do not stack (see How light follows the hour). A GPU renderer must not add a third.
Planned (plan 42): one period record for every map, read by both renderers; an effect
never invents a colour, a direction or a strength, it takes them from that record.
Present holds only quality: on or off, resolution, sample counts, strengths named by
what they do.
Determinism
Section titled “Determinism”- Structure.
pl-presentis reachable only from the parts that build pictures:pl-game’s view builders, the desktop and the DS platform. A test reads every crate’s manifest and fails if a logic crate depends on it. - Draw-only data. Rows that draw more (draw distance, widescreen, particles) load extra data into caches owned by the view, never into the world; weather particles use their own hash, never the game’s random numbers.
- The replay proof. A recorded session is replayed at
classicand atultra, and with the accessibility rows on, and the world’s and battle’s state digests, every save and the logs must be equal tick by tick. A planted leak fails it.
The proof’s details are on Presentation and game state.