ASA Manager: save, assign and restore configurations

Saved Configs are reusable gameplay and INI settings. They are separate from server-world backups and mod bundles. Earlier screenshots may use the older menu name Configurations.

1. Create a named configuration

1. Open Saved Configs in the left menu.
2. Click New configuration.
3. Enter a descriptive name such as Boosted PvE.
4. Edit the intended Game.ini and GameUserSettings.ini settings.
5. Click Save config and review the changes before confirming.

Step illustration

The page’s INI panel is a read-only preview. Use Edit configuration to open the editor. Saving in the editor is distinct from saving an individual server profile.

2. Capture settings from a server

1. Select the source server and review its current effective settings.
2. Use Save as config from the server’s saved-configuration controls.
3. Give the captured configuration a unique name.
4. Review and save it, then reopen it from Saved Configs.

Capturing a configuration does not automatically mean every server is assigned to it. Confirm the assignments explicitly.

3. Assign it to servers

1. Select the configuration and click Manage assignments.
2. Tick the servers that should share it.
3. Check the list before clicking Save assignments.
4. Start/restart the affected servers when ready for the new settings to take effect.

Shared configuration changes apply at each assigned server’s next start, not immediately to a live game. Maps, server names, passwords, ports, cluster identity and mod IDs stay server-specific.

Step illustration

4. Edit and duplicate safely

1. Select a Saved Config and click Edit configuration.
2. Change the intended values only.
3. Save config and review the affected server names.
4. Use Duplicate when you want to make a new variation rather than change the original shared settings.

A change to a shared config affects every linked server. Check assignments before saving a production-wide adjustment.

5. Import or export INI files

In the editor, Import Game.ini and Import user settings load INI text into the configuration for review. Save config stores the reviewed result. Export INIs writes a copy of the current draft to your chosen destination; it does not itself assign that draft to a server.

Reserved server-specific credentials and launch identity are not intended to be distributed through shared configs. Always inspect exported files before sharing.

6. Restore a previous version

1. Open Edit configuration, then Previous versions.
2. Choose the intended revision from the saved history.
3. Click Load into editor.
4. Review the loaded values.
5. Click Save config to commit the restoration for linked servers.

Loading into the editor alone is not a completed restoration. History keeps the last 20 saved configurations; keep exports for longer-term archives.

7. Unlink or delete

Unchecking a server in Manage assignments returns it to its own settings. To retain the current effective shared values as independent settings, use Make a separate copy from that server’s shared-config controls and review/save it.

A linked configuration cannot be deleted until its servers are unassigned. Delete config removes that saved settings record, not the server installations or world saves.

Exact gameplay values