Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/kaladoodotlua/KCSH/llms.txt

Use this file to discover all available pages before exploring further.

KCSH requires no installation or configuration — the entire hub is delivered by a single loadstring call that fetches and executes the latest source.lua directly from GitHub. There are no files to download, no folders to set up, and no settings to tweak before you start. As long as your executor can reach the internet and run loadstring, you are ready to go.

Prerequisites

Before executing KCSH, make sure you have:
  • A supported Roblox exploit executor with loadstring and game:HttpGet enabled (e.g. Synapse X, KRNL, Fluxus, or any equivalent level-7 executor).
  • An active Roblox game session — KCSH must be injected while you are inside a running game.

Execute KCSH

1

Join a Roblox game

Open the Roblox client and join any game. KCSH is game-agnostic — it works in any title because all of its features operate on client-side humanoid and workspace properties.
2

Open your executor

Launch your exploit executor and attach it to the running Roblox process. Wait for the executor to confirm a successful injection before proceeding.
3

Paste the loader

Copy the one-liner below and paste it into your executor’s script input box:
source.lua
loadstring(game:HttpGet("https://raw.githubusercontent.com/Kaladoo2/KCSH/refs/heads/main/source.lua"))()
4

Execute

Click Execute (or your executor’s equivalent button) to run the script. KCSH intentionally waits before building the GUI — first a task.wait(0.5) pause while it resolves the local player and workspace character, then a second task.wait(1) pause after the ScreenGui is created — so expect roughly 1.5 seconds before the panel appears on screen.
5

Interact with the panel

The semi-transparent white panel appears in the center of the screen. Click any button to toggle that feature on or off. To reposition the hub, click and drag anywhere on the panel background — it will smoothly tween to follow your cursor using TweenService with a 0.3-second Quad ease-out.

What happens on execution

When the script runs, it first performs a cleanup pass: it calls pcall to search game.CoreGui for any existing child named "KCSH" and destroys it if found, preventing duplicate panels from stacking up if you execute the loader more than once. It then creates a fresh ScreenGui with ResetOnSpawn = true, sets its DisplayOrder to 2147483647 so it always renders above every other GUI, and parents it to game.CoreGui. After the second task.wait, the script builds the main draggable frame: a 300 × 312.5 px Frame with 50 % background transparency, a white fill color (RGB 255, 255, 255), and a UICorner with a 25 px corner radius for the rounded look. The frame uses TweenService + UserInputService events to implement smooth drag-to-reposition behavior. Inside the frame lives a ScrollingFrame (invisible scrollbar, automatic canvas height) with a horizontal-wrapping UIListLayout. The script populates this scrolling area by calling makebutton() for each feature toggle and maketext() for section headers, building the full button list from top to bottom: the hub title label, all movement feature buttons, the extras buttons, a “Player Teleports” section label, and then a dynamically populated sub-frame of per-player teleport buttons.

Toggling features

Every feature button uses Roblox’s RichText system to display a colored status indicator inline with the button label. When a feature is disabled, the status reads off in red (#a63131). When a feature is enabled, it switches to on in green (#39a637). The button text is updated directly on each click by reassigning the button’s .Text property — no separate status label is needed.
If the KCSH panel disappears after your character respawns, you will need to re-execute the loader script. This is expected behavior: the ScreenGui is created with ResetOnSpawn = true, which tells Roblox to automatically destroy the GUI whenever the local player’s character resets. Simply paste and execute the loadstring one-liner again to bring the panel back.

Build docs developers (and LLMs) love