Modern Input production persistence
Updated 2026-11-18. This report describes the version 0.3.0 implementation; the plugin's profile guide is the current source of operational instructions.
Storage boundary
The main mod INI contains only preferences and commented value ranges. Binding files are associated with named game profiles and stored under %LOCALAPPDATA%\NFS Underground 2\ModernInput\profiles. They are separate from the original career save format. Complete native serialization of all mod-managed axes, buttons and family variants has not been demonstrated, so the implementation does not modify that format.
Each sidecar separates controller family and slot. Fields are explicit validated lists, not ABI-dependent hexadecimal structure dumps. Saves use a temporary sibling, file replacement and a previous-file backup. Read failures can recover the previous complete section; write failures retain session controls and schedule a retry.
Guest bindings are session-only. A player-profile change changes the storage context even if the native controller channel address is unchanged. The existing protection against global/native controller table resets remains scoped to the current named profile.
Native identity: US 1.2
| Address | Evidence |
|---|---|
0x0083A9E0 |
Player 1 name, 32-byte zero-terminated buffer |
0x0083AA00 |
Byte at Player +0x20; the named-profile flag used by native save/profile logic |
0x00502FD0 |
Returns ECX as the name pointer; called with Player 1 by profile UI |
0x00502FE0 |
Returns the byte at ECX +0x20 |
0x00515AA0 |
Clears the player name, restores a localized default and sets +0x20 to zero |
0x005124A6 |
Tests the Player 1 flag before restoring default-name state |
0x00532458 |
Uses the flag when choosing a named profile in native save logic |
These facts were checked against the existing local US 1.2 disassembly, not inferred solely from a third-party address list. yugecin's Player/ProfileData documentation provided useful external symbol cross-references; no code was imported.
The plugin guards both native accessor prologues, reads only 33 bytes and rejects non-terminated/default identities. One identity snapshot is used for each storage operation. Identity polling is shared between channels, with explicit refreshes on capture/reset.
Legacy migration
The upgrade helper backs up the old INI, preserves its v2 bindings in a legacy source and writes the new commented template. The first named player claims migration ownership, including when the currently selected controller family has no old section. Other players cannot import that global source. Existing v3 mappings take precedence, and the legacy source remains available for rollback.
Validation boundary
Software tests exercise separate profiles, family/slot isolation, guest behavior, native synchronization on profile changes, migration ownership, malformed inputs, write failures and backup recovery. A separate upgrade-helper test checks preservation and installation locking.
The previous 0.2.0 gameplay report does not validate the new profile identity at runtime. A real migration/profile-switch/restart test is still required for 0.3.0. Physical PlayStation/Switch devices and racing wheels remain unverified.
Removed experiments
The production plugin no longer contains the LAA/header experiment or the fake diagnostic wheel. Their old reports remain historical research, not active product features. Real wheels still pass through to the game's native DirectInput implementation.