How quantumxternal/jew-dick-hack works
This is a Windows Roblox process-inspection overlay with player visualization, gameplay-modification features, and scripting interfaces. The main lifecycle attaches to the Roblox process, starts player caching, and runs the renderer/UI; on process exit it clears runtime state and reconnects. The tree and settings expose substantial feature families, but the README is empty and most feature wiring was not sampled, so those links are omitted or marked unverified rather than inferred. Evidence is limited to the supplied source excerpts and SOURCE INDEX references.
Main entry points: Settings.h Feature settings · Main.cpp Application lifecycle · PlayerHandler.cpp Player cache · Handlers.h MCP handlers
Components 23
Runtime and data
- Application lifecycle
src/Main.cpp - Process memory
src/core/memory/Memory.h - Player cache
src/core/player/PlayerHandler.cpp - Roblox object model
src/core/roblox/classes/Classes.h - Feature settings
src/app/Settings.h
Gameplay features
- Aim features
src/features/aim - Movement features
src/features/movement - Local modifications
src/features/local - World features
src/features/world - Game-specific features
src/features/games
Visuals
- ESP and overlays
src/features/visuals/ESP.cpp - Chams rendering
src/features/visuals/EngineChams.cpp - Raycast engine
src/features/visuals/RaycastEngine.cpp - Visual effects
src/features/visuals
User interfaces and scripting
- Overlay renderer
src/renderer/Renderer.cpp - Configuration menu
src/gui/Menu.cpp - Instance explorer
src/features/explorer - Lua execution
src/features/lua/LuaExecutor.cpp - MCP bridge
src/features/mcp/McpBridge.cpp - MCP server
src/features/mcp/execute/Server.h - MCP handlers
src/features/mcp/handlers/Handlers.h
Other components
- Operator
- Roblox process
Connections 28
- Operator → Application lifecycle: starts
- Application lifecycle → Process memory: attaches
src/Main.cpp - Process memory → Roblox process: reads process
src/core/memory/Memory.h - Application lifecycle → Player cache: starts cache
src/Main.cpp - Player cache → Process memory: reads process
src/core/player/PlayerHandler.cpp - Player cache → Roblox object model: uses objects
src/core/player/PlayerHandler.cpp - Application lifecycle → Overlay renderer: starts overlay
src/Main.cpp - Overlay renderer → Configuration menu: runs UI
src/renderer/Renderer.cpp - Application lifecycle → Raycast engine: resets state
src/Main.cpp - Application lifecycle → Visual effects: clears avatars
src/Main.cpp - MCP server → MCP handlers: dispatches
src/features/mcp/execute/Server.h - MCP handlers → Process memory: uses process access
src/features/mcp/handlers/Handlers.h - MCP handlers → Roblox object model: uses objects
src/features/mcp/handlers/Handlers.h - MCP handlers → Feature settings: uses settings
src/features/mcp/handlers/Handlers.h - Operator → Configuration menu: configures
- Configuration menu → Feature settings: changes options
- Operator → Lua execution: runs scripts
- Operator → Instance explorer: inspects instances
- Operator → MCP server: requests actions
- Feature settings → Aim features: controls
- Feature settings → Movement features: controls
- Feature settings → Local modifications: controls
- Feature settings → World features: controls
- Feature settings → Game-specific features: controls
- Feature settings → ESP and overlays: controls
- Feature settings → Chams rendering: controls
src/features/visuals/EngineChams.cpp - Player cache → ESP and overlays: supplies players
- Player cache → Chams rendering: supplies players