Manage sessions and profiles

A profile is saved configuration. A session is one open use of that profile. Closing a session does not delete its profile, automations, map, packages, or logs.

When a connection ends, smudgy keeps the session open so you can read its scrollback. Use the reconnect action in the session to connect the same profile again. A new connection starts a new raw log if raw logging is enabled; ordinary logging resumes in a new timestamped file after a reconnect.

Repeated disconnections usually point to the MUD or network rather than the profile. If the failure occurs before any MUD text appears, check the saved server address and TLS settings in Connect.

In the Connect window, choose Offline beside a profile. Smudgy loads its map, modules, packages, aliases, triggers, and hotkeys without opening a network connection.

Offline mode is useful for editing a map or repairing an automation that prevents a normal login. Press Connect in that session when you are ready to go online.

Create one profile per character so each can have its own description, password, and commands sent on connect. Profiles under the same server share saved aliases, triggers, hotkeys, modules, packages, maps, and logs. Creating a profile does not make a private copy of those tools.

When an automation should run for only one character, organize it in a clearly named folder and make its script check the current profile. A non-scripted saved automation cannot be marked profile-only.

Do not create a second server entry merely to add another character unless it uses a different network address or connection settings.

Open Connect, select the server, then use the edit control beside the server or profile. Removing a profile deletes that profile's login details and protected password; shared server automations, packages, maps, and logs remain. Removing the server deletes all of its profiles and server-scoped files. Back up the server first if you may need any of it. See Data files and backups.

You can open more than one profile at a time. Pay attention to the window title and current output before sending commands: command history, hotkeys, and scripts act in the session that owns the focused input. Also check the MUD's rules before using more than one character simultaneously.