Field batch 1 readability follow-ups (bridge decision tree, bridge-shaped API, accessor names) #46
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From the independent readability review of PR #35 (2026-11-03), items left for later (not blocking the merge):
UpdateObjFramebridge repeats the game's decision tree (core/port/field_bridge.c~264-290): use a bridge-local path enum + oneswitch; factor the repeated entry checks (8-bit A with B=0, 16-bit indexes, field pages) into oneprv_field_entry_ok(). Watch the bridge:game ratio (#38 should cut it).field_objects.hexports 8 functions, the game needs 2;field_scroll_speedlikewise. Group them under a "helpers also used by the bridge" comment or accept as convention;field_object_walk_stepint + out-parameter could be one return value.re/ram_map.toml):field_bg_scroll_carry-> scroll overflow,field_objects_map_ptr-> map cell, scratch accessors (field_obj_frame_facing_base,field_obj_frame_anim_offset,field_scroll_step) get ascratch_prefix so game code does not use them as state.