Sessions: game, script, memory, and recovery
Contents
Configuration location
Select an account → Account settings → Accounts & sessions:
| Section | Purpose |
|---|
| Account setup | Individual settings for selected accounts |
| Launch & status | Launch plans, confirmation, processes, history |
| Memory | Group presets and available measurements |
| Backups | Settings import/export and layout saving |
Main-table selection controls visible cards. Profile selection inside settings controls group-command recipients. Review names in the plan before confirming.
Settings
| Setting | Meaning |
|---|
| Roblox account | Saved account used by the profile |
| Folder | Logical account group |
| Recovery | Game/VIP, attempt count, failure delay |
| Reconnect if Roblox closes | Allows recovery for the launched client |
| Start when ExtraExecutor opens | Starts when required account data is available; locked vault prevents launch |
| Auto-attach after launch | Tries the helper after client discovery |
| Send selected script after attach | Sends the assigned file after attachment |
| Script | Saved file in Scripts or Autoexec |
| Apply memory preset on launch | Applies a saved limit to the new process |
| Clear isolated temporary cache | Clears this profile's temporary directory after exit |
Disabling auto-attach disables automatic submission and signals. Disabling recovery disables automation. Changing the linked account also disables automation until reconfigured.
Example: one account, one script
- Save
main.luau in Scripts. - Select the account, choose the file in Script, and save.
- Set a Place ID or Place ID + VIP in Recovery.
- Enable Auto-attach and Send selected script after attach.
- Optionally enable Reconnect if Roblox closes.
- Launch & status → Review selected launches → check account/game/script → Confirm launch.
Assign a different file to a second account; settings are individual. Timers use the saved account scenario and do not replace the file.
Game and VIP
Recovery accepts a Place ID or full Roblox HTTPS URL /games/number/.... Private servers have a separate field. privateServerLinkCode can be extracted from a full game URL. A private URL takes precedence.
Short share/VIP URLs may need a separate Place ID. A server Job ID is not a private link. Recovery stores placeId/privateServerUrl and does not promise a persistent main-form Job ID join.
Without a target, manual launch may open the Roblox app. Automatic recovery/automation requires a saved target. Enabling game-script signals without one opens Recovery; successful saving enables signals, cancellation leaves them off.
Failures and recovery
Close the failed process and start a new one
Use Session settings → Enable crash reconnect, or Auto reconnect: close failed Roblox and reopen saved game. It also enables auto-attach/signals; without existing automation it creates a signals-only configuration with a 90-second heartbeat timeout.
The monitor tracks process exit, persistent window hangs, missing first/subsequent heartbeat, and unconfirmed entry into the saved game. The bridge polls visible Roblox ErrorPrompt every 2 seconds if CoreGui access exists. Kicks/network errors may be detected; complete coverage of every version/dialog is unconfirmed.
Only the profile's verified PID/process instance is closed. A new process waits for confirmed exit. If closure fails, history records the error and delayed close retries occur without spawning duplicates.
Unconfirmed-entry timeout is at least 120 seconds; persistent-hang threshold at least 45 seconds. Individual heartbeat timeout may extend these. After 60 seconds of fresh reports matching the saved Place ID, consecutive recovery failures reset. Unhealthy new clients remain bounded by the attempt limit.
New sessions use saved game/VIP and attachment/script settings. Submission occurs only when its individual option is enabled. Native monitoring tracks Windows process instances, not merely numeric PIDs. After exit, cache cleanup, delay, and a bounded retry may follow. Attempts: 1–20; delay: 1–3600 seconds.
Stop recovery for this run cancels future actions; it does not close Roblox. Account removal also leaves live Player running.
Opt-in timers/disconnect requests can terminate a verified profile process and schedule recovery. This differs from passive exit monitoring. General discovery failure must not be treated as a crash.
Some errors require runtime bridge events and may remain undetected. Cooperating scripts can explicitly use ReportDisconnected.
Memory
Memory cap limits process committed memory through a Windows Job Object; it does not reserve physical RAM. Presets: 128–65536 MiB.
- Save preset stores the value.
- Apply limit targets the confirmed live process.
- Apply on launch targets a new launcher process.
- Apply memory cap on next launch can be enabled before Save preset: with no preset, it saves the valid current input, default 1024 MiB. An existing preset is not replaced by an unsaved draft.
- Remove/unlimited removes the managed limit where possible.
Working set and commit are different measurements. Summed working sets may include shared pages. Unavailable means no measurement, not zero usage. A low cap can cause out-of-memory failures; raise/remove it before retrying.
Cache
Launcher profiles receive isolated TEMP/TMP under session-cache. Cleanup affects only that directory after exit, not Roblox global assets, browser cookies, or unrelated folders. Roblox may store data elsewhere.
During cleaningCache, relaunch is delayed/rejected. For busy files, inspect history; do not delete all of %LOCALAPPDATA%\Roblox as a general fix.
Backups
Backup v2 includes names, groups, memory presets, and script references only. It excludes script contents, cookies, account binding, VIP secrets, live process bindings, startup/attach/submit, recovery, automation, and cache options. Import supports v1/v2. Relink accounts and review settings after import.
Use Retry save on write errors. Dialog closing/switching waits for persistence to avoid silently losing changes.