Introduction

Overview

KrulHub is a Roblox script hosting platform. Public scripts are open-source — run the loadstring, accept the consent popup, and the script loads immediately. The source is readable; you can fork or self-host any of it.

Open source
Every public script ships with credits to its original authors. Read it, fork it, or self-host it — your choice.
Consent popup
A small in-game GUI asks you to confirm before the script loads. No key required.
Serverless
Runs entirely on Cloudflare Workers. No VPS, no downtime risk from hardware.
Introduction

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.

Check your executor. If you are unsure whether your executor supports sUNC, consult its official documentation or community. Running on an unsupported executor is not a KrulHub issue.
Platform age requirements. KrulHub has no age gate, but Roblox requires users to be at least 5 years old and Discord requires at least 13. Make sure you meet the requirements of any platform you use.
Usage

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.

Loadstring format
loadstring(game:HttpGet("https://krulhub.dev/s/<script-id>"))()
1
Execute the loadstring
Paste it into your executor's script box and hit Execute. The consent popup appears in-game.
2
Accept the consent popup
Read the script name shown in the popup and press Continue to proceed. Press Cancel to abort.
3
Script runs
The script source is fetched from krulhub.dev and runs in your executor. Source is open and readable; you can fork or self-host any time.
Usage

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.

Script errors immediately after accepting
This is almost always an executor compatibility issue. Verify that your executor meets the sUNC standard. Outdated executors may be missing functions the script depends on.
HttpGet fails / cannot reach server
Your executor may have HTTP requests disabled, or the Roblox game has restricted HttpService. Ensure your executor has HTTP enabled. KrulHub scripts cannot function without outbound HTTP access.
Community & Tools

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

  1. Click Login in the top nav and authenticate with Discord.
  2. You must be a member of the KrulHub Discord server. Join it via the link on the homepage if you haven't already.
  3. 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.

Cooldowns. Per-account rate limits apply. If you hit a cooldown, wait for the countdown to expire before submitting again.
Community & Tools

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

  1. Configure a bundle you want to share inside the Ro-Clothes script.
  2. Press Submit Bundle in the script UI. A confirmation is shown if accepted.
  3. The submission lands in a moderation queue. A reviewer checks it and either approves, rejects, or marks it as spam.
  4. 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.

Rate limits. Submissions are rate-limited per UserId (hourly + daily) and per IP. If you hit a limit, the script will show "try again in ~Nm".
Spam marks trigger bans. Submitting clearly junk or duplicate bundles can trigger a temporary ban on your Roblox UserId. Put real effort into submissions.
Community & Tools

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.

Disclosure. Entries are readable by any client that knows your server's placeId:jobId pair. In practice this is just other users in the same Roblox server, but if you don't want to share any of this, leave the toggle off.
Fully revocable. Turn the toggle off and your entry expires within 300 seconds. Nothing persists longer.
Community & Tools

Diagnostics Telemetry (opt-in)

The Ro-Clothes script can optionally send anonymous diagnostic events to KrulHub so we can find and fix bugs we can't reproduce locally. The toggle is OFF by default; nothing is sent unless you turn it on.

Enabling it

Open the Settings tab inside the Ro-Clothes script and flip the Send Anonymous Diagnostics toggle. A confirmation modal lists the event types being captured and shows the queued events before anything leaves your machine.

What gets sent

  • Event names like install.chunk_fail, hd.apply_throw, capture.spoof_detected.
  • The script version (e.g. V4.3.520.0524).
  • Your executor name (from identifyexecutor()) and platform class (Desktop / Mobile / Console).
  • Small structured fields per event — file paths, error codes, durations, counts. Capped at 4 KB per event.
  • A random "install ID" (UUIDv4) generated on first enable and persisted locally. It is NOT derived from your Roblox UserId, your Discord ID, your IP, or any account identifier.

What is NEVER sent

  • Roblox usernames, display names, or any in-game text.
  • Chat content or anything you've typed.
  • Accessory or catalog IDs you own, or place names.
  • The Roblox jobId, your IP, or anything that can link an event to a real person.

Local-only log (always on)

A diagnostic log is also written locally to RClothesLerp/diagnostics.log for your own self-diagnosis. This is filesystem-only and never leaves your machine unless you copy it. It exists whether the network toggle is on or off.

View pending before sending. The diagnostics panel has a "View Pending" button that shows the exact events queued for upload. Nothing is uploaded without your action; "Send Now" force-flushes the queue if you want immediate feedback.
Fully revocable. Toggle off and uploads stop immediately. Pending events are cleared. To delete telemetry already received, share the first 8 characters of your install ID (visible in "View Pending") on Discord and we will purge matching objects.
Help

FAQ

Do I need an account or key to use scripts?
No. KrulHub does not use a key system. Run the loadstring, accept the in-game consent popup, and the script loads immediately.
The script worked before but now returns an error
The script may have been updated or taken offline. Check the homepage for the current list of available scripts and grab the latest loadstring if one is listed.
The consent popup appeared but nothing happened after I accepted
This is almost always an executor compatibility issue. Verify that your executor meets the sUNC standard — missing API functions will cause a silent fail after the popup closes.
A script I used before has disappeared
Scripts can be taken offline at any time. If a loadstring returns an error, the script may have been removed or updated. Check the homepage for the current list of available scripts.