Executors
Note: For the best experience, use Potassium. Wave is also fully supported. Untested executors may work but have not been verified. Unsupported executors will show a warning but may still attempt to load. Blocked executors stop execution.
Why are some executors unsupported?
Executor Capability Requirements
Our scripts depend on more than basic execution. They need stable startup behavior, hidden UI support, desktop-style input, Drawing support for overlays, hook support for some games, and a reliable scripting environment. Low-coverage executors usually miss one or more of these requirements.
WEAO + Manual Overrides
WEAO provides live status and API coverage data. We use that data for visibility and default untested entries, but our manual compatibility rules are the final source of truth because our scripts have game-specific requirements.
Game-Specific Requirements
Different games have different executor requirements. SSRP relies on stable startup validation and UI compatibility. RC2 primarily needs file APIs for persistence and server hopping. Naramo modifies weapon configuration directly. EA depends on stable hook support for combat remotes. Game-specific overrides are supported when an available script needs one.
Why mobile executors are blocked
Mobile executors like Delta, Cryptic, Vega X, and Codex can have strong API coverage, but our scripts are designed around PC gameplay. Silent Aim requires mouse input, the UI is built for desktop screens, and keyboard shortcuts control many features. We block mobile executors to prevent a broken experience.
Unsupported vs. Untested vs. Blocked
Supported executors are verified to work. Untested executors may have the technical capability but have not been verified. Unsupported executors are known to not work well. Blocked executors stop execution entirely because the experience is expected to be broken.