First launch and files
Contents
Application package
Extract the entire release folder and run ExtraExecutor.exe. Keep bin, DLLs, and the application together. One copied EXE is not a complete package. Production omits the separate console entry point; see distribution.
| Item | Purpose |
|---|
| ExtraExecutor.exe | Editor and Account Manager without a console window |
| ExtraExecutor-console.exe | Separately built version of the same application with a console |
| Start-ExtraExecutor-Server.cmd | Starts the console version and keeps the console open after exit |
| bin | Existing helpers/payload, including bin/Potassium.exe and bin/Potassium.dll |
| DLLs beside the application | Required Windows/WebView libraries |
| scripts.lnk, autoexec.lnk, workspace.lnk | Open the current user's local folders |
| logs | Application logs |
| account-manager | Instructions, examples, license, and package checksums |
| documentation | This complete guide in newer packages |
Avoid running both entry points simultaneously: they are two instances that may compete for one port.
User data
Default root: %LOCALAPPDATA%\Potassium, under the current Windows user, not the developer's build directory.
| Folder/file | Contents |
|---|
| scripts | Saved user scripts |
| autoexec | Scripts in the automatic execution section |
| workspace | Working files |
| accounts.dpapi | Encrypted account sessions |
| account-profiles.json | Encrypted profile settings; the extension does not imply plain text |
| settings.json | Shared application settings |
| session-cache | Isolated temporary profile directories |
| AccountDumps | JSON files created by Dump Details |
Some interface settings also reside in WebView localStorage. This is not a complete application backup.
New package shortcuts initially create/open user folders through hidden PowerShell. After launch, the application updates them to direct directory links. Do not overwrite them with old shortcuts from another computer.
First steps
- Open ExtraExecutor and sign in with your website license key or linked Discord account. The editor does not require a Roblox account; desktop sign-in is separate. See website sign-in.
- Open Accounts on the left of the top bar.
- Create a local password or unlock the existing vault.
- Add an account and wait for Saved @username.
- Select it and open Account settings.
- Assign a game and script for automatic actions.
- Review and confirm the launch in Launch & status.
Initial logical sizes: ExtraExecutor 1000×640; Account Manager 900×480, minimum 800×450. Windows DPI can change physical pixel dimensions. Later launches retain position but use the base size; previous maximization is not restored.
Updating without losing data
Close old instances. Extract a new portable package into a separate directory and launch the new EXE. The same Windows user's data stays in its existing folder. For Setup updates, see installation.
Before manual changes, copy the local data folder while the application is closed. Profile backups exclude login sessions. A DPAPI copy does not guarantee restoration on another computer or Windows account.