mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-16 18:09:58 -04:00
cfg.c takes a value as written and logged nothing about it: "pace_smooth = 0 ; off" keeps the comment in the value and cfg_bool reads it as on, "fullscreen = false" is on too, and "sharpness = 250" is past 0..100 (the audit's probe on cfg.c printed exactly that, with 0 log lines during the load). A player who edits the file by hand had no way to see why a setting did not take. After cfg_load (and after migrate, so a value it rewrites is checked as read) each file value is checked against its row: a 0|1 switch with any other value, a value that is not a number in a lo..hi range, and a word that is none of a list of words, case aside. A list with a number in it is left alone: it is the menu's presets and its consumer takes more (fps_limit any rate from 30 to 240). A list of words is reported as "none of the menu's choices" only, since a consumer may take more (dlss_preset a..m). A value holding " ;" or " #" is noted on any row: the comment is part of it. cfg_init checks the environment's NX2NAVI_ values the same way. At most 16 lines a load, then a count. The values read are unchanged; reading words for off or cutting comments (F-8) needs approval. Not reproduced before the change by a game run; the new tests/cfg_parse_check.py builds cfg.c with stand-ins and checks each kind of line with its line number, the environment's, the cap of 16 and a count, and no line for a file whose values fit (including fps_limit 144, render_scale 300, dlss_preset k, pad_layout xbox_prompts). Every value nx2navi.ini.example shows passes without a line. launcher_test PlayerIniTest, the cfg rows check and the compile checks pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4.9 KiB
4.9 KiB