Kaiju Paradise private-server controls are best discovered from the command help available in the current server. Community references describe a command bar or chat-style syntax, but the exact prefix, aliases, permissions, targets, and unlocks can change. Use this page as a safe test workflow rather than an unsupported exhaustive command dump.
Open current command help
Create or join a private server you are authorized to manage. Let the current interface load, then look for the private-server command panel or help control. Community documentation reports help aliases such as help, cmds, or cmd, sometimes with a chat prefix. Treat those as discovery leads.
If the visible command bar provides autocomplete, use it. It exposes the server’s current spelling more reliably than an old page. Submit the help action without a player target first and read permission or syntax errors exactly.
Never test moderation commands in a public server or against players who did not agree. Private-server ownership does not grant authority outside that server.
Command groups to expect
Test an event command safely
Community pages report Power Outage aliases such as poweroutage or po and Blackout aliases such as blackout or bo. They also report that event commands can require the owner to have survived the corresponding event. Do not present those conditions as permanent until the current help confirms them.
Before starting an event, tell every test player, record the normal room state, and choose a recovery landmark. Start one event only. Observe lights, electronics, barriers, doors, buttons, interface information, and event objects. End or reset it using the current help rather than guessing another command.
Test transformation controls
Community documentation describes transformation commands, sometimes abbreviated tf, and links availability to Bestiary progress. Open help to find the exact current form identifiers. A display name may contain spaces or differ from the internal command token.
Use your own account as target first. Record the visible resulting form and action bar. Reset before testing another form so acquisition, mutation, and event effects do not overlap. Do not use transformation controls to claim a public acquisition route.
Target players carefully
Self first
Use a self selector or your exact current username when supported. This limits mistakes while learning syntax.
Exact target
Do not rely on a short prefix when two usernames are similar. Read the confirmation or error.
One action
Change one player state at a time and confirm the result before chaining another command.
Recovery
Know how to reset, rejoin, or remove a temporary restriction before testing a stronger control.
Moderation cautions
Kick and ban behavior can persist differently. Before using a ban-like action, inspect whether help shows duration, unban, list, or reset controls. Confirm the exact username and state the reason to participants. Do not test persistent moderation on the only owner account.
Avoid scripts, executors, or off-platform admin downloads. Legitimate private-server controls are provided by the game. A third-party tool asking for a Roblox cookie or credential is not required for command access.
Build a current command record
For each command you reproduce, record visible name, alias, required permission, target format, arguments, success response, failure response, side effect, and reset path. Add the server date and whether the command was shown by current help. This turns a fragile list into a repeatable reference.
The command UI, help aliases, event controls, transformation controls, Bestiary gates, and moderation categories are community reported from Kaiju Paradise documentation checked August 13, 2026. The source page itself is marked outdated, so exact syntax not shown by current help remains unverified.