Side by side with Roblox, never inside it.
Lemon Clix lives in its own process. It reads what the game already exposes and drives real input, so there is no module of ours sitting in the client.
What's inside
One menu over the game, four things you will actually keep on.
Aim
Aimbot, silent aim and triggerbot share one target, so the crosshair and the shot never argue about who they are on.
Visuals
Boxes, skeleton, health, flags, and chams that sit in the depth buffer instead of painting over the map.
Silent aim
Viewport and mouse-hit ship free. Raycast, magic bullet and XYZ engines are on the premium side.
A tab per game
Supported titles get tools written against the way that game stores its own state, not a generic profile.
Why keep it external
Two processes, one game. That single decision is what keeps the menu boring and the account quiet.
Nothing injected
No DLL in the client, no module for the anti-cheat to walk through. Memory is read, input is sent, both from our side.
Idle means idle
Disabled features cost nothing. Nothing is written to the game until a feature needs it.
Update day is fine
The offsets feed is pulled at launch and matched against the running build, so a patch does not silently turn everything off.
Made per game
Rivals, Phantom Forces, Da Hood and the rest get tools shaped around their own mechanics.
Games with their own tab
Aim and visuals are universal. These four are not.
Rivals
Skin changer with the full weapon list, applied straight from the menu
Phantom Forces
Dedicated silent engine and team detection, aimed at the way PF builds its characters
Da Hood
Loadout markers, grapple break, a tracker that follows the chase
Arsenal
Instant target switching and a weapon-first ESP layout
Take it for a spin
Grab the build, open the menu over the game, and read the setup post in the Discord if anything looks off.