Glossary
Each term is defined as this site uses it. Where a word has more than one sense in PokeLoom (profile, preset, scene), each sense is given.
Actor. A character placed on a map’s events layer: a sprite, a facing and a way
of moving. A script refers to it by the name it has in Tiled. See
People and characters.
Area file. What the build makes of one map: its cells, its meshes chunk by chunk and its events, in a form the DS reads in place. See Files a project holds.
Art set. For each asset role, the pieces (3D style) or metatiles (tile style) that
draw it in one style, in art/<set>/artset.toml. Choosing another art set changes a
game’s look without touching its maps. See
Asset roles and style chains.
Asset role. A name for a kind of thing in the world, such as tree.small, grass
or house, with a default behaviour and footprint but no look. Maps place roles and
art sets draw them; a role no art set draws falls back to its parent. See
Asset roles and style chains.
Bank (text). A file of the text/ folder: strings read from the pack when one of
them is shown, so a large game’s text need not sit in memory. text.txt is always
loaded; the four banks used last are kept while they fit in 32 KB. See
Text and dialogue.
Battle ground. The ground a battle is begun on (grass, sand, water and so on),
which chooses the platforms the creatures stand on, apart from the battle scene. A
map sets it per cell on its battle_ground layer. See
Battles and trainers.
Behaviour. What a cell is to walk on: blocked, grass, water, a ledge, ice and the
rest. Pieces give a default and the map’s behavior layer overrides it. See
Maps.
Billboard. A flat picture that always lies in the plane of the screen, however the camera turns. Generation-4 games draw their people this way; PokeLoom does too where a game asks for it. See Flat characters and their shadows.
Camera zone. A rectangle of cells, drawn as a camera object on a map’s events
layer, where the field camera takes a framing of its own while the player is inside.
See Cameras.
Cell. One square of a map’s grid: 16 × 16 pixels in Tiled and one unit in a model. A cell holds a ground piece, at most one object piece, a height from 0 to 31½ levels, a behaviour and a tag. See Maps.
Chunk. A block of 32 × 32 cells: the unit the engine stores, meshes and streams. A map in a world starts on a chunk’s edge, and two maps may not own one chunk. See The joined world, zones and warps.
Conformance. Checking a built-in battle rule against Pokémon Showdown: the same battle with the same random numbers is played in both, and their traces must match. No built-in mechanic is done without it. See Battle rules checked against Showdown.
Content source. In a style chain, the game that owns the story: its maps, flags, trainers, text and scripts. Other sources contribute only art. See Asset roles and style chains.
Digest. A short hash of the game’s logic state (the world, the scripts, the battle), logged every few ticks. Two runs that should agree compare digests, so a difference is found at the tick it starts. See Determinism.
Edge marking. The DS’s outline: where opaque polygons with different polygon IDs meet, the hardware draws an edge in one of eight colours. PokeLoom draws it as melonDS does. See Toon, edges, anti-aliasing, fog.
Event. Something placed on a map’s events layer: an actor, a sign, a trigger, a
warp, the start or a camera zone. The map’s script answers it with on talk,
on read or on step. See Scripts and events.
Family. A kind of menu screen (party, summary, bag, storage, dex, the Start menu, signs). Its behaviour is written once; its look is a style. See Menus and UI styles.
Flag. A saved yes-or-no value a script sets and tests; a game has 4,096. A
variable is the same for a number. Both are named in .pfsym files. See
Scripts and events.
Frame commands. The description of one frame that the game fills each tick in the DS’s own terms (tile layers, sprites, one 3D scene) and that a backend draws: the DS on its hardware, the desktop in software. The game never knows which. See One description of a frame.
Fx. The shared fixed-point number type. Logic that runs on the DS uses no floating point, so the same sums give the same results everywhere. See Determinism.
Gadget. A device on the lower screen, such as the Pokétch or the C-Gear. Planned
(plan 45): a gadget is a shell (the device’s frame, buttons and skins) and a set of
apps registered by script. Today the lower screen has the [ui.bottom] styles. See
Gadgets and the lower screen.
Golden image. A screenshot kept as the expected result of a test. A change that alters it fails until the new picture is looked at and accepted. See Testing.
Hook. A script the engine runs at a moment rather than for one object on a map:
when a map loads, on a new game, when an item is used, when a wild creature is about to
appear. Editing hooks (on wildmon, on trainerparty, on givemon) may change what
the engine is about to do. See Scripts and events.
Import. A one-way conversion of a game you own (a ROM or a decompilation) into an editable project, for your own use only. See Importing games.
Input log. The record of every tick’s input (and the clock, the network and other players), four bytes a tick. Playing it back gives the same game exactly. See Determinism.
Layout record. The file that holds every number and picture of a built-in menu
style: layouts/<family>.toml with its pictures under graphics/menus/<family>/.
A project edits it freely; the behaviour stays the engine’s. Planned (plan 45): every
screen, the battle interface and the title are records, the engine’s own look being
the default record. See Menus and UI styles.
Light set. The plans’ word for a light table: a game’s lights for each period of the day. See Light table.
Light table. The light of a map through the day, period by period: for each
period, the four hardware lights’ directions and colours and the materials’ colours.
The engine has four (day, bright, dim, warm); a game adds or replaces them in lights.toml,
and a map names one with light. See
Light, time of day and weather.
Metatile. A 16 × 16 pixel block of 8 × 8 tiles, in layers below and above the characters: one cell of a tile map, as GBA games draw their worlds. See The tile-map (GBA) style and How GBA tile worlds work.
Overlay. A project’s own files laid over another project’s by ploom sync, so a
game can tell another’s story on its own data, or the reverse. See
Importing games.
Pack. pack/game.pak, the one file ploom build makes from a project and the
engine loads on every platform. It is made, never edited or checked in. See
Building and shipping.
Package. Planned (plan 46): a versioned folder of data, scripts and optional Rust
that a game adds with ploom add. See Packages.
Pairs. Pictures of the real game and of PokeLoom at the same map, cell, hour and story state, with the difference counted by a tool rather than judged by eye. It is how an import’s fidelity is measured. See Fidelity by pairs.
Period. A part of the day that starts at a set time and has its own light. When the clock passes into the next period the game changes the colours, so one map looks like morning, evening or night. See How light follows the hour.
Piece. What a map is built from. A ground piece is a 16 × 16 tile of a texture; an
object piece is a model with a footprint and a behaviour. Pieces are listed in
maps/pieces.toml. See Maps and
Art: pieces, models and pictures.
Polygon ID. A number from 0 to 63 every DS polygon carries. Edge marking draws outlines where opaque polygons of different IDs meet, and translucent polygons with one ID do not darken each other. See Toon, edges, anti-aliasing, fog.
Preset. A named set of values chosen at once. A camera preset is a whole
framing: pitch, distance, field of view (Cameras). A
presentation preset (classic, high, ultra, auto) sets every graphics row
(Presentation settings). A rule preset such as
wild = "heartgold" sets a system’s numbers to one game’s
(Battle rules and gimmicks).
Profile. Three senses. game.toml is the game’s profile: its settings in
groups, so two games differ only in settings (Game settings).
An import profile is the format knowledge for one game, such as gba-emerald
(Importing games). On desktop, ds and wide are the two
display profiles (One wide screen on desktop).
Replay. Playing an input log back. A replay gives the same game on every platform, which makes every recorded session a test. See Determinism.
Scene. Two senses. A battle scene is the picture of the place a battle is fought in front of (Battles and trainers). An engine scene is one layer of the running game: the field at the bottom, with the title, a battle or the ending pushed over it. Planned (plan 46): scenes a game adds in Rust. See Scenes and the world grid.
Session (test-nds). A named run of cargo xtask test-nds: a program or project and
the input logs it plays, on desktop with no window and in melonDS. Both must write the
same log and show the same screens. See Testing.
Source. A ROM, a decompilation or another project that a project draws from,
listed in sources.toml and read into a cached source image. See
Asset roles and style chains.
Style. A built-in look and behaviour for one menu family, taken from one game (Platinum’s party screen, Emerald’s Start menu). See Menus and UI styles.
Style chain. The list of sources, in order, that draw a game’s world by role:
[content] names the story’s source and [style] world the sources tried for art,
with pins for single roles. It is how one game’s world is drawn in another’s art. See
Asset roles and style chains.
Tag. A number from 0 to 255 on a cell, set on the map’s tag layer, that scripts
can test. See Maps.
Tick. One step of game logic. Logic runs at 60 ticks a second on every platform; input is read once a tick and nothing else enters it. See One description of a frame.
Trigger. Cells on a map’s events layer that run a script when the player steps on
them (on step). See Scripts and events.
Variant. A map’s file swapped for another when the map loads, chosen by a flag or a variable: the same place before and after the story changes it. See Map settings and variants.
Warp. A way from one map, or one cell, to another: a door, stairs, a hole, a panel. Its kind says how it is taken and how the move looks. See The joined world, zones and warps.
World. A set of maps placed on one plane of cells, drawn with one set of textures, one light table and one fog, and walked from map to map with no fade. See The joined world, zones and warps.
Zone. A map seen from inside a world: its name, music, weather, people, scripts and wild creatures. Crossing into another zone changes those without a load. See The joined world, zones and warps.