Potassium
Potassium is the one you pay for, and it lets you look before paying: the file here is a demo with an hour on the clock, and the licence that keeps it running comes from a developer site we could not confirm. It runs Lua and Luau inside the game, on Windows.
Windows PaidThe download here is the demo. It runs for one hour so you can try it, and after that it asks for a licence bought from the developer's site. We do not have a confirmed link to that site, so we do not link to one. The licence is the whole of the payment: nobody who sells an executor needs your Roblox password, and nobody needs your card details to run a script.
At a glance
| Detail | Potassium |
|---|---|
| Platform | Windows PC |
| Price | Paid: the download here is a one-hour demo |
| Language | Lua / Luau |
| Main function | Running scripts |
| Key system | Licence or authentication |
| Compatibility | Depends on the Roblox version |
| Ban risk | Yes |
| File checked | Yes, tested and virus-scanned |
Screenshots
Pick one to see it at full size.
What it is
The first thing to know about Potassium is the price: an hour as a demo, then a licence from the seller's site, on Windows only. The name follows a line of executors named after elements, since potassium is K.
It is presented as the work of the Byfron Bypass Team, a group behind several projects of this kind, and it sells itself on one thing above the rest: how quickly it recovers after Roblox patches its anti-cheat. That promise is what the licence pays for, and it is also the thing that is hardest to check from the outside.
What it can do
Three things decide what a script can reach: the game you are in, the script itself, and whether the two fit. What follows is the usual shape of it:
Visual and environment changes
- Adjust the fog, the field of view, the lighting and the skybox.
- ESP: see where other players and objects are.
- Fullbright, no-fog and chams, plus HUDs and overlays you draw yourself.
- Replace textures or models locally.
Automation
- Farming loops left running in Blox Fruits, Pet Simulator and similar.
- Auto-clickers and macros, with conditional logic.
- Movement bots and local teleports.
- Aim assistance, where a script provides it.
Interacting with the game
- Play animations, sounds and effects.
- Change the client's own interface.
- Simulate input: keyboard, mouse, taps.
- Intercept the game's own functions and redirect what they do, locally.
Advanced scripting
- Load script hubs (Rayfield, Fluent, Kavo, Orion).
- Put an interface of your own on screen, inside the game.
- Let scripts talk to each other through
getgenv(). - Keep a configuration in a file and load it next session.
- Debug with the built-in console.
None of these are necessarily built into Potassium: they depend on the script you run.
Requirements
| Component | Detail |
|---|---|
| Operating system | Windows 10 or 11, 64-bit |
| Processor | Any modern x64 |
| Memory | 8 GB recommended |
| .NET | Framework 4.8 or newer |
| Permissions | Administrator rights, because it handles processes |
| Roblox | The current version |
| Antivirus | One exclusion, usually. Injecting code into another process is what a scanner is watching for. The installer behind the download has already been scanned before it went up. |
| Licence | Paid: the demo gives you one hour, then a licence is needed |
Download Potassium
Windows, and our gate comes first. This is the demo: one hour to try it, and a licence comes from the developer.
How easy it is to use
- Installing it is simple: download it, run it as administrator, attach it to Roblox.
- The interface is modern, with an editor, several scripts in tabs and a console.
- Running scripts somebody else wrote needs nothing beyond loading it: writing your own sits in the middle, because it means Luau. Hooks and metatables, the advanced parts, are hard.
- Getting started is better covered than most of the competition: guides in their Discord and documentation of their own.
- When something goes wrong the console reports the error, keeps the logs and shows how long the script ran.
Community
Because it costs money, the crowd around it is smaller than the free executors' and leans more technical. The licence buys support as much as software, and support lives in these places:
- A Discord run by the team, which doubles as the support channel.
- YouTube, for demos, tutorials and script reviews.
-
Reddit, in
r/robloxexploitsandr/robloxhackers. - GitHub, where the scripts and the interface libraries live, though the executor is not there.
- Exploit forums, where the older threads on it live.
New hubs, scripts, libraries and interfaces turn up there all the time, and per-game configurations get passed around as well.
Strengths and weaknesses
What it does well
- Stability after a Hyperion patch is the team's stated priority.
- Fast, both to inject and to run.
- A broad API that still runs scripts written for Synapse X.
- Support from the team, in their Discord.
- A filesystem, so scripts can keep a configuration.
- Multi-instance, and auto-exec.
- A modern, organised interface.
- Frequent updates, which is what the licence pays for.
Where it falls short
- It is paid, which is a barrier next to the free executors here.
- Windows only.
- The bypass is the weak point: a drastic change to Hyperion can leave it unusable for a while.
- A smaller community than the free executors have.
- Sparse documentation next to Synapse's, which is the bar.
- A licence check, or a key system on some builds.
- Being paid attracts look-alike sites, with contradictory claims about versions and licences. Check where a link comes from before you follow it.
Hubs, libraries and extras
Plugins are not a thing here. What it does have is an ecosystem, built from the following:
Script hubs: a whole interface, ready to use
- Rayfield UI, the one most scripts use.
- Fluent, which looks like Windows 11.
- Kavo UI, minimal.
- Orion, modern and modular.
- Obsidian, for the more complex interfaces.
Support libraries
- WindUI, Lunar and Linoria, among others.
What comes built in
- Auto-execute when it attaches.
- A scripts folder, with some organisation.
- A console with live output.
- Several scripts at once, in tabs.
- Save and load the ones you use.
- A filesystem, so a script can keep files and read them back later.
Compatibility
- High with the Synapse X API, so the many scripts written for it still run.
loadstring(), for scripts kept at a URL.- External modules through
require().
Potassium and Xeno
A paid one and a free one, side by side. The numbers are what the vendors and the directories announce, not tests run here:
| Aspect | Potassium | Xeno |
|---|---|---|
| Price | Paid | Free |
| Main platform | Windows | Windows |
| Announced compatibility | 99% UNC | More limited |
| Decompiler | Yes | Depends on the version |
| Detection risk | Yes | Yes |
| Approach | Advanced features | Free access |
Potassium announces wider compatibility than Xeno, and that is not the same thing as being safer: a higher percentage of implemented functions says nothing about whether the tool can be detected or about a ban.
Status and safety as of 10 October 2026
Before you try it, this is where things stand:
- Detection. On 2 October 2026 a developer published a method on Roblox's own forum to detect Potassium's injection by the way it handles console errors. Third-party tracking lists the current build as detected.
- Third-party numbers. ScriptBunker lists Potassium 2.5.2 with a listed price of $22.99 USD, a lifetime licence, a last recorded update of 8 October 2026, and announced UNC of 99% and sUNC of 100%. None of that is ours and none of it is tested: a high UNC or sUNC means the scripting functions are implemented, not that the tool cannot be detected.
- Which site is the real one. Several sites present themselves as official, with contradictory claims about versions, licences and platforms. The demo here is the one we checked; the licence itself comes from the developer, and we link to no site of theirs.
- What can change. One Roblox update can move any of this, and more than one already has.
Download Potassium
Windows. The demo runs for one hour; after that it needs a licence from the developer. Older builds are below.
Get Lua code for:
After the Lua for one particular game? Put its name in the search: the page for that game lists the code, the codes its creator published, the tricks, and the guides that go further. Nothing there costs anything.
How it works
What the demo does with its hour, what the licence covers, and the API waiting inside. The injection itself is the same story for every tool in the list.
The file offered here is the demo, and the hour is the whole of it. It attaches to the client like the paid build and stops when the clock runs out, so what can be judged in that time is the panel, the editor and whether the scripts you already use run without errors. A licence then comes from the seller's site, paid for there and never inside the program.
What the money maintains is the bypass and the builds on top of it. Every version is repackaged after a Roblox patch, with the payload obfuscated and the DLL kept out of the scans, and memory is reached through a signed but vulnerable driver (BYOVD) rather than one of the team's own. Handles get hijacked as well, so the ones a scan reads are not the ones doing the work. When Hyperion changes, the tool waits for the next build: a version older than the last patch is worth nothing, whatever number it carries.
Inside the client the API follows the Synapse X standard rather than a smaller set of functions. The rest of the machinery, from injection to what a script cannot reach on the server, is shared with the other tools and is explained once in how an executor works. This is the environment a script meets:
| Category | Examples |
|---|---|
| Environment |
getgenv(), getrenv(), getreg(),
getgc()
|
| Instances |
game, workspace,
Instance.new(), cloneref()
|
| Metatables |
getrawmetatable(), setreadonly(),
hookfunction(), hookmetamethod()
|
| Network |
firetouchinterest(), fireproximityprompt(),
fireclickdetector()
|
| Execution |
loadstring(), require(), pcall(),
spawn()
|
| Utilities |
getconnections(), getsignal(),
checkcaller()
|
| Filesystem |
readfile(), writefile(),
listfiles()
|