How chimeralle-real/externalexecutor works
ExternalExecutor is a Windows-based Roblox script executor: it locates Roblox processes, prepares and installs initialization bytecode, then accepts source for execution through an exported entry point. The README also advertises a separate desktop UI and UNC/SUNC compatibility, but the UI form and bridge implementation were not sampled, so their detailed wiring and those capabilities’ implementation are uncertain.
Main entry points: ExternalExecutor.cpp Executor entry · Instance.hpp Instance access · Bridge.hpp Bridge · Bytecode.hpp Bytecode utilities
Components 13
Desktop interface
- Desktop UI
ExternalExecutorUI/Form1.cs
Executor runtime
- Executor entry
ExternalExecutor/ExternalExecutor.cpp - Bridge
ExternalExecutor/Bridge.hpp - Connection setup
ExternalExecutor/Dependecies/server/server.h
Roblox integration
- Process discovery
ExternalExecutor/Utils/Process.hpp - Process memory
ExternalExecutor/Utils/Memory.hpp - Instance access
ExternalExecutor/Utils/Instance.hpp - Runtime offsets
ExternalExecutor/Update/Offsets.hpp
Luau toolchain
- Luau compiler
ExternalExecutor/Dependecies/Luau/Compiler.cpp - Bytecode utilities
ExternalExecutor/Utils/Bytecode.hpp
Other components
- User
- Roblox process
- Target scripts
Connections 14
- User → Desktop UI: uses
- User → Executor entry: calls Nuke
- Executor entry → Bridge: starts bridge
- Bridge → Connection setup: sets up connection
- Executor entry → Process discovery: finds processes
- Executor entry → Instance access: locates datamodel
- Instance access → Process memory: reads and writes
- Instance access → Runtime offsets: uses offsets
- Executor entry → Bytecode utilities: compiles and signs
- Bytecode utilities → Luau compiler: compiles source
- Executor entry → Instance access: replaces script bytecode
- Executor entry → Roblox process: targets process
- User → Target scripts: supplies source
- Executor entry → Target scripts: executes source