Cloud config reverted after the loader update

Configs

Create config, save config, load config, delete config. I thought one “ABI main” profile was enough. Then I loaded it on Valley after an Armory night and aimbot FOV was still 6.

Need a naming scheme that survives ACE patches without deleting the good one by accident.

10 replies

Replies 10

From the thread

u/map_prefix·5 days ago

northridge-safe, valley-long, armory-close, farm-loot. Never “main”. Load by map in the stash screen before you ready up.

u/cloud_first·4 days ago

Save to cloud after every good raid. Local-only configs vanished on me after a loader update.

u/delete_old·4 days ago

Delete anything with a date older than the last ACE bump. Stale FOV values are worse than starting over.

u/cfg_mess·4 days ago

I had three “final” configs. Deleting the dated ones now.

u/clone_then_edit·3 days ago

Create from a clone of northridge-safe. Do not edit live and hope you remember to save.

u/aim_vs_vis·3 days ago

Some people split aimbot-only and vis-only. I still prefer per-map because corpse filters change more than smoothness.

u/portal_order·2 days ago

Load config in the portal first, then launch Steam. Overlay-first sometimes boots last session.

u/backup_usb·36 hours ago

Export once a week. Cloud is great until you click delete on the wrong name at 2am.

u/status_reload·20 hours ago

After ACE updates, reload the config even if the name is the same. Sliders can reset silently.

u/duo_share·8 hours ago

Do not share raw cfg files in Discord DMs. Use the portal invite if you even need to. Most “shared” files are stale anyway.