Cleanup and Exit Pipeline

The ghost cleanup flow coordinates launcher, native, and Java layers to shut down modules cleanly. This process is designed to reduce leftover runtime traces and keep sessions predictable between launches.

The practical sequence is: stop active module logic, unwind injected hooks and class transforms, unload native components, and clear temporary artifacts. This staged approach avoids abrupt teardown that can leave broken state behind.

Step 1

Signal Shutdown

Launcher/ejector signals the runtime to stop active automation and begin controlled teardown.

Step 2

Disable Active Modules

Java payload disables running modules and unregisters hooks to stop gameplay-side actions safely.

Step 3

Retransform / Unload

Class transformations are rolled back where supported, then native loader components are detached.

Step 4

Trace Cleanup

Cleanup routines remove temporary artifacts and close IPC resources for a cleaner post-session state.