Many ARK mods read their configuration from a dedicated [ModSettings] section of GameUserSettings.ini rather than from the standard sections. The mod author documents their keys (often on the CurseForge page or in a README). AASM v0.8.3 exposes this section through the Mod Manager so you don't have to hand-edit the .ini.
Prerequisites:
Server tab → Mod Manager. Find the mod whose settings you want to edit in the Active list.
Click the gear/settings icon on the mod's card. AASM opens the per-mod settings editor showing every key currently in the [ModSettings] section attributed to this mod, plus any keys you've added previously.
Use the editor to add new keys or change existing values. Common patterns:
SomeFeatureEnabled=TrueMaxStacks=1000CustomChance=0.5Mod authors set the key names - copy them verbatim from the mod's docs. AASM doesn't validate them against the mod's expected schema (it can't - the mod hasn't declared one).
Click Save. AASM writes the [ModSettings] section back to GameUserSettings.ini using a case-insensitive section/key matcher (v0.8.2 fix, BUG-ModSettingsCaseInsensitive) so existing keys are updated in place instead of duplicating into a new section.
v0.8.2 / v0.8.3 concurrency: simultaneous mod-settings edits from desktop + Web UI on the same server are now serialised via per-server locks (BUG-ModWriteRace). Earlier builds could lose changes if you saved in two places at once.
ARK reads GameUserSettings.ini at server startup. Restart the server (or wait for the next scheduled restart) for the mod to pick up new values.
Once a mod loadout works, take a Settings Snapshot. Snapshots capture the full [ModSettings] section via ModConfigService.setModSettings() on restore (selective restore was a v0.8.2 polish), so you can roll back per-mod tuning without losing it.
Per-mod settings live in [ModSettings] and AASM edits them safely with case-insensitive matching and per-server locks. Snapshot them once you're happy with the loadout.