Introduction

Overview

KrulHub hosts community scripts. Browse the available loadstrings and inspect source at /source/<script-id> when public viewing is enabled. Some loaders ask for confirmation; others run immediately. Reuse depends on the script author's license or permission.

Source viewing
Inspect a script before running it when public source viewing is enabled for that script.
Per-script prompt
A script may show an in-game confirmation before loading. Public scripts need no KrulHub key.
Serverless
Delivered through Cloudflare Workers with KV, R2, and Durable Object storage.
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 of its own. You must meet the age requirements of each platform you use; see the Roblox Terms of Use and the Discord Terms of Service.
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
Review the script
Open /source/<script-id> when public source viewing is enabled and run only code you trust.
2
Execute the loadstring
Paste it into your executor and run it. If a consent prompt appears, press Continue to load or X to cancel.
3
Script runs
When a script's prompt is disabled, its payload starts immediately after the loadstring runs. Reuse rights depend on the author's license or permission.
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
A download, service, or executor compatibility error can stop the script. Check HTTP access and executor support, then report the error if it continues.
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

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:

  • 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 KrulHub stores

The moderation record contains the bundle contents, script and manifest versions, submitter name, request IP, and timestamp. It identifies the submitter by Roblox UserId or, for a signed-in Discord submission, Discord ID. See the Privacy Policy for retention details.

Rate limits. Submissions are rate-limited per Roblox UserId or signed-in Discord ID, and per IP. A limit response includes a retry time.
Spam marks trigger bans. Marking a submission as spam applies a seven-day ban to the Roblox UserId or signed-in Discord ID used to submit it.
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)

Ro-Clothes can send optional diagnostic events to help identify faults. Diagnostic uploads are off by default. The loader's Roblox UserId online-count heartbeat is a separate feature.

Enabling it

Open the Settings tab and enable Send diagnostics (Ro-Clothes V4.5.32+) to send diagnostic batches. Review the pending events in the diagnostics panel before sending.

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 installation ID generated on first enable and stored locally. It links events from the same installation.

The diagnostic event format accepts structured error fields. Check "View Pending" for the actual values queued by your script version. KrulHub uses the request IP in a short-lived telemetry rate limit, and administrators can inspect stored raw events.

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 shows queued event details. Diagnostic uploads start only after the diagnostics toggle is enabled; "Send Now" sends queued events immediately.
Stop future uploads. Turn the toggle off to stop diagnostic uploads. To request removal of batches already received, open a private ticket in the KrulHub Discord server and share the installation-ID prefix there.
Help

FAQ

Do I need an account or key to use scripts?
Public scripts need no KrulHub key or account. A script may display a consent prompt or load immediately, according to its setting.
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
The payload may have failed to download, or the executor may lack an API it needs. Check HTTP access and executor support, then report a persistent error.
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.