RAM map: width doubts (bg_scroll_pos +3, event_loop_count, the_end_rng_index) #16

New issue

Open

opened 2026-10-29 10:17:15 +00:00 by Gatchan · 0 comments

Gatchan commented

2026-10-29 10:17:15 +00:00

Owner

Open questions from the RAM map slice 1 (refs #7), to settle by the ports that own these values:

bg_scroll_pos (struct, 4 bytes): the notes give 3 bytes, the code writes 4 with 16-bit stores. Is byte +3 ever read?
event_loop_count: notes say 3 bytes per entry, InitNewGame writes 1 byte.
the_end_rng_index: 16-bit index with an 8-bit increment; is $0501 guaranteed 0 when the stars start?

Each entry has an open key in re/ram_map.toml.

Open questions from the RAM map slice 1 (refs #7), to settle by the ports that own these values: - `bg_scroll_pos` (struct, 4 bytes): the notes give 3 bytes, the code writes 4 with 16-bit stores. Is byte +3 ever read? - `event_loop_count`: notes say 3 bytes per entry, InitNewGame writes 1 byte. - `the_end_rng_index`: 16-bit index with an 8-bit increment; is `$0501` guaranteed 0 when the stars start? Each entry has an `open` key in `re/ram_map.toml`.

Gatchan added the

task

label

2026-10-29 10:17:15 +00:00

Gatchan referenced this issue from a commit

2026-10-29 10:20:20 +00:00

docs: RAM map slice 1 in re/ram_map.toml, format and decisions in docs/ram_map.md (refs #7)

Gatchan referenced this issue

2026-10-29 10:37:17 +00:00

RAM map slice 1, generated state accessors, peek/poke by name #18

Gatchan referenced this issue

2026-10-29 10:40:35 +00:00