Skip to content

Accessibility

Plan 44 gathers the settings players of modern fan games expect into one design: accessibility, battle, challenge modes and convenience (decision 314). Each is behind a setting, and each is placed by one question: does it change only how the game looks, or does it change the game?

Class What it is Lives in Same on desktop and DS? Who changes it
P, presentation changes only pixels (or a sound not played) the device file, never the save may differ the player, any time
O, game option part of the game the save’s options rows the same the player in the options, if the creator shows the row
C, challenge rule chosen at a new game, fixed after the save’s rules the same the player at a new game, among what the creator offers
D, device pace the same ticks, run faster the desktop’s config only desktop only the player; the creator may cap it

The line between P and O is strict. A row that changes when the game reads input changes the game: the tick a choice is made, the input log, what a co-op partner sees. So battle speed, which looks like animation, is a game option, not presentation. The replay proof of Presentation and game state catches a mistake: a presentation row read by the game’s logic fails it.

Accessibility rows are presentation rows with two extra rules: a game can never cap or forbid them (decision 315; the build refuses such a cap), and presets never change them. They are off by default.

Row Choices Desktop DS State
colour_vision off, protanopia, deuteranopia, tritanopia, greyscale 2D palettes at load, the 3D picture after it is drawn every palette at load, and the clear, fog and outline colours built
less_motion off, on shakes drawn as none, the party curtain as a fade the same code built in part
less_flashing off, on brightness flashes eased the same code built in part
text_size normal, large, largest text drawn at two or three times over a scaled picture hidden: the DS’s fonts and boxes are fixed the row is built; drawing is planned
high_contrast off, on boxes and menus from a high-contrast skin a palette set at load planned
hud shown, hidden hides the field’s own overlays, not the text box the same planned
type_colours off, on type names on their type’s colour the same planned
low_health_beep on, once, off the warning beep always, once a battle, or never the same planned

The filters correct, they do not simulate. Each is one 3 × 3 integer matrix applied to colours: it takes the difference between colours that a viewer with that kind of colour vision would confuse and moves it into the channels they see. White, black and greys are kept. greyscale turns every colour into its brightness.

Because a DS draws every colour from a palette, the filter is applied as palettes are loaded, with no cost per frame and no tables. On desktop the 2D palettes are filtered the same way, so 2D pixels equal the DS’s, and the 3D picture is filtered after it is drawn, which is exact under coloured light. On the DS, light and material colours are not filtered, so a scene under a coloured evening light is close rather than exact.

A change takes effect at once on desktop. On the DS it takes effect at the next load, because palettes already in video memory are not filtered again.

Both rows keep every tick count. An effect still takes as long; it is drawn calmer. That is what keeps replays and co-op identical with the rows on or off.

  • Less motion, built: the field camera’s shakes (a warp’s landing, the shake command) and a move animation’s screen shake are drawn as none; the party screen’s curtain is a fade over the same ticks. Planned: the battle camera’s motion, the location banner’s slide, a hit creature’s wiggle, slides and flips in menus drawn as cuts at their midpoint.
  • Less flashing, built: brightness flashes change by at most a sixteenth a tick (heavy rain’s lightning, a move animation’s brightness). Planned: a move animation’s background colour swaps and tints, and the low-health blink.

The row exists on desktop. Drawing text at two or three times its size needs the desktop’s picture composed at a higher scale first.

Planned (plan 44, plan 42): text in boxes, menus and the touch screen drawn at 2× or 3× from the font’s own glyphs over the scaled picture, on desktop only.

Plan 45 describes a larger text size differently, as a save option where typed text re-wraps into more pages and every menu record carries a large layout. Which of the two designs is kept is not settled.

Planned: high contrast, HUD, type colours, the beep

Section titled “Planned: high contrast, HUD, type colours, the beep”

Planned (plan 44): a high-contrast skin (black frames, white ground, text with a contrast ratio of at least 7 to 1); hiding the field’s own overlays (a script’s meter, the banner, follower icons); type names on their type’s colour in the move menu and summary; and the low-health beep played always, once or never.

Today the rows are set in the desktop’s config file or on its command line (--set colour_vision=deuteranopia), and on the DS in its device file. Planned (plan 44, plan 42): an accessibility part of the Graphics page in the options, on desktop and DS.

Planned (plan 44):

Row Class What it does
battle_speed O animations and text at double pace
battle_scene O move animations on or off
hp_drain O health bars drain as the original, or at a fixed pace
battle_log O a touch-screen page listing the turn’s lines
quick_run, quick_ball O in wild battles, B jumps to Run, R throws the last ball
foe_health P the foe’s box shows a percent beside the bar
move_cards P the move under the cursor shown in full: type, category, power, accuracy, priority, contact, why it is disabled
field_counter P weather, terrain, screens and hazards with turns left
battle_camera P the battle camera’s motion: the game’s, calm or still

The game options are rows of the options screen that a creator shows or fixes at a default; they are saved with the game, so a replay at either speed gives the same battle.

Chosen at a new game and fixed after, seeded by the save’s seed so they are the same on every platform.

Mode State
Challenge mode: a fainted creature is lost to a box or released; the game ends when none can fight built ([rules.challenge])
Level caps built ([rules] level_cap)
Nuzlocke lives and ledger: a number of faints before the rule bites, the first meeting of each route recorded, presets of named rules planned (plan 44)
Seeded randomizer: a shareable seed and categories (wild, trainers, starters, gifts, learnsets, abilities, items, evolutions), with rules that keep the game playable; tables made at load from the seed, never stored planned (plan 44)
Soul Link for two players: creatures caught on the same route are paired, and a faint ends both planned (plan 44, after co-op saves)

A creator offers modes in game.toml; the player picks among them on a new-game page.

Planned (plan 44):

Row Class What it does
auto_run O holding B walks, so running is the default
autosave O saves on a map change or every few minutes of play, counted in ticks so a replay saves at the same tick
soft reset engine a button combination returns to the title; a creator may turn it off
day_length C or O the real clock, or a day in 24, 60 or 120 minutes of play
speed-up D 1× to 4× while a key is held or toggled; desktop only, off in link and co-op play; a creator may cap or forbid it

The desktop already runs faster while Tab is held; the setting, its cap and its proof (a replay at 4× equals one at 1×) are planned.

A game’s own options and rules, beyond these, are game data: [ui.options] rows, [rules], and scripts that read them. See Rules, options and cheats.