Thread: iGO sys editor

iGO Sys Editor — Feature Overview

Core database

514 parameters across 24 categories, covering all three engine variants: nextgen_32, luna_64, luna_32
Every parameter carries: name, section, default value, list of valid options (where applicable), per-version compatibility flags, and descriptions in 5 languages (Slovak, English, Russian, Slovenian, Turkish)

Editing

Each parameter row shows one always-editable value field — type directly, or click it to get a dropdown of known-valid options (custom-built list, not relying on the browser's native datalist, since that proved unreliable)
Clicking the parameter name shows its full explanation in the status bar; clicking the value is reserved purely for editing
Built-in range/format validation for specific fields (e.g. dpi 96–640, TMC download radius ≤200 km)

File handling

Load an existing sys.txt, parse it, and edit it directly
Auto-detects which engine version a loaded file is for — but never silently overrides a version you've picked yourself; if the file looks like a different version, it tells you and asks rather than switching underneath you
Export a clean sys.txt back out
Save/restore full session profiles (JSON), undo/redo history

Smart export logic

"Skip values matching iGO's built-in default" — with a review list showing exactly which parameters match, each individually checkable to keep or omit
Two-tier confidence: values verified directly against real device config files are marked (✓), versus values inferred from the general default field (·) — never presented as equally certain
A fixed set of parameters (TMC, memory, driver-alert distances, engine_1.1 voice config, focus/resume behaviour, etc.) are always written regardless of the skip setting, because omitting them breaks functionality — and this list itself respects per-version compatibility, so it never forces a Nextgen-only key into a Luna export or vice versa
Detects parameters that are flatly incompatible with the currently selected version and offers to remove them

Everything behind it is evidence-based, not guessed

Defaults, valid option lists, and compatibility flags have been cross-checked against real APKs (native library strings, decompiled Lua, and actual shipped config files from real devices) rather than assumed — and corrected multiple times over this project when better evidence turned up