ExtraExecutor — complete documentation
Documentation version: October 22, 2026. Covers the current local project build. Button names match the application.
Contents
- First launch and folders
- Editor, Run, Attach, console, and settings
- Accounts, password, and manager actions
- Launching, assigned scripts, memory, and recovery
- Roblox signals, timers, and multiple accounts
- Troubleshooting
- Feature status and known limitations
- Development, builds, and maintenance
- Log completion rules, MCP, and Dex++
- AND/OR builder, sequences, HTTP, Studio, and AI clients
- Standalone Luau VM
- Standard/Production, protection, installation, and updates
- Website sign-in, Discord, keys, and releases
- Device protection and HWID binding
Quick reference
| Task | Location |
|---|---|
| Add an account | Accounts → Add Account → Manual Login |
| Assign a script | Select account → Account settings → Accounts & sessions → Account setup → Script |
| Set game/VIP | Recovery in the same profile |
| Submit automatically | Auto-attach + Send selected script after attach |
| Reconnect on a timer | Session cache, script signals & schedule → Connection interval |
| Script recovery request | PotassiumSession API |
| Memory limits | Memory and individual profile cards |
| Saved scripts | %LOCALAPPDATA%\Potassium\scripts |
| Run has no effect | Run/Attach troubleshooting |
Readiness terminology
Implemented means a code path exists. Builds successfully means compilation succeeded. Verified in game would mean an actual live-client run; this build does not have that complete confirmation.
submitted means delivered to the client, not executed. running means a process is tracked, not that it joined the intended server. Documentation describes existing behavior; it does not implement missing features.