Overview
KrulHub is a private Roblox script hosting platform. Scripts are obfuscated and encrypted server-side. No key needed — run the loadstring, accept the consent popup, and the script loads immediately. Nothing plaintext ever leaves the server.
Requirements
Before you can run any KrulHub script, make sure you have the following:
Executor
A sUNC-supported executor is required. sUNC (Standard UNC) is a compatibility standard that defines which Roblox API functions an executor must implement. KrulHub scripts rely on several of these functions — using an executor that does not meet the sUNC standard will result in errors or a silent fail.
Consent Popup
When you run a KrulHub loadstring, a small in-game GUI appears before the script executes. This is the consent popup — it tells you the script name and asks you to confirm before anything runs.
What it does
- Shows the script name — so you know exactly what you're about to run.
- Requires a click to proceed — the script will not load until you press Continue.
- Can be dismissed — pressing Cancel aborts execution with no side effects.
Running Scripts
Each script on KrulHub has a unique loadstring. Find it on the homepage under Available Scripts, copy it, and execute it in your executor.
Error Messages
The in-game GUI displays a short status message when something goes wrong. Here's what each one means and how to resolve it.
HttpService. Ensure your executor has HTTP enabled. KrulHub scripts cannot function without outbound HTTP access.User Obfuscator
The user obfuscator is a self-service Lua obfuscation portal. Paste a Lua script, pick a protection level, and get back an obfuscated version you can use anywhere.
Getting access
- Click Login in the top nav and authenticate with Discord.
- You must be a member of the KrulHub Discord server. Join it via the link on the homepage if you haven't already.
- Once signed in, head to
/obfuscate.
Protection levels
Four levels are available, from light string protection up to full 8-layer pipeline (control-flow flattening + VM + recipe-encoded constants). Higher levels are slower to execute and larger in size — pick the lowest that meets your needs.
Saved scripts
Your recent obfuscation outputs are saved to your account so you can retrieve them later without re-obfuscating. Slots are scoped to your Discord ID and only visible to you. You can delete any slot at any time.
Ro-Clothes Submissions
The Ro-Clothes Roblox script ships a curated bundle library that anyone running the script can browse. Users can contribute their own bundles to that library in two ways:
- Bundle Creator (web) — build and submit a bundle from your browser at krulhub.dev/bundle-creator. No executor needed.
- Submit Bundle (in-script) — if you're already running the Ro-Clothes script in-game, hit the Submit Bundle button in its UI.
How to submit
- Configure a bundle you want to share inside the Ro-Clothes script.
- Press Submit Bundle in the script UI. A confirmation is shown if accepted.
- The submission lands in a moderation queue. A reviewer checks it and either approves, rejects, or marks it as spam.
- Approved bundles are published to the community chunk library and become visible to all Ro-Clothes users on their next manifest refresh.
What moderators see
Your submission includes the bundle contents, your Roblox UserId, your Roblox display name, the script version, and the submission timestamp. See the Privacy Policy for retention details.
Avatar Sync
Avatar Sync is an opt-in feature in the Ro-Clothes script that lets other opted-in users in the same Roblox server see your custom bundle rendered on your character in real time. Useful for showcasing custom outfits to friends in the same game.
Enabling it
Open the Settings tab inside the Ro-Clothes script and flip the Avatar Sync toggle. It defaults to off.
What gets shared
- Your Roblox UserId and display name.
- Your current bundle.
- The Roblox placeId and jobId of the server you are in.
The sync is scoped to one Roblox server instance — only other opted-in users in the same server see your bundle. State lives on the server for 300 seconds after your last publish and then auto-expires.