Your setup travels with the app.

Where preferences live

AIM-X stores persistent preferences in settings.jsonc beside AIM-X.exe. The folder must be writable. The GUI Save action writes to the same file.

Edit without rebuilding

1. Close AIM-X so a GUI save cannot overwrite your edit.
2. Back up settings.jsonc.
3. Edit existing entries, keeping their names and value types.
4. Launch AIM-X again. The file becomes this session’s startup preferences and reset defaults.

// Example entries inside the existing JSON object:
"preview/1/Mode": 1,          // 0 = God, 1 = Human
"preview/1/Auto fire": true,
"window/animations": true,
"controls/activation/aim": 2  // Right mouse button (virtual-key code)

Line comments, block comments, and trailing commas are accepted. Value-only saves preserve existing comments; structural changes may normalize the document.

What is included

Canonical UI preferences, colors, bone selection, assigned hotkeys, window preferences, and migration markers. Missing new preferences are added on upgrade.

What is not restored as authority

Input masters, attachment state, and live telemetry are session state. A saved preference does not bypass runtime gates. License credentials remain in the Windows-encrypted credential cache, not plaintext JSONC.