Backup and Restore Basics

Use this guide to avoid losing profiles, script groups, and key settings.

Save Profile vs Save Character

MudBringer uses two save scopes that should be treated differently:

1. Save Character: Saves character-specific data and independence (scripts, aliases, actions, variables, connection identity).
2. Save Profile: Saves profile-level workspace behavior (layout context, dashboard arrangement, and profile-scoped multi-session setup).

For stable recovery, use both save paths during major changes.

What to Back Up

Prioritize these items:

1. Character profiles.
2. Script groups and custom automation.
3. Dashboard/layout configuration.

Backup Rhythm

Use a simple cadence:

1. Create a backup before major script imports.
2. Create a backup before large refactors.
3. Keep at least one weekly rotating backup.

Quick Backup Checklist

1. Close active risky edits.
2. Run Save Character for each important character.
3. Run Save Profile for the active profile.
4. Name backups with date and purpose.
5. Store a second copy off your main machine when possible.

Example naming:

• main-profile-2026-05-25-pre-import
• squad-layout-2026-05-25-weekly

Restore Workflow

When recovering from a bad change:

1. Identify the last-known-good backup.
2. Restore character data first.
3. Restore profile data.
4. Restart MudBringer.
5. Validate connection, aliases, and triggers.

Window Placement Persistence

Window placement is saved to the profile when the app closes.

Practical rule:

1. Finish layout changes.
2. Close the app cleanly so profile window state is persisted.
3. Re-open and verify expected placement.

Recovery Triage

If things still fail after restore:

1. Disable newest script imports first.
2. Re-check session host/port values.
3. Verify automation groups are enabled.
4. Compare with a clean profile if needed.

Next Steps

1. Installing Community Script Packs Safely
2. Managing Sessions and Tabs
3. Trigger Fundamentals (Patterns, Actions, and Groups)