There is no verified public command list yet
No exact INFs ADMINS in SAE admin commands list is published on the current Roblox experience page. The safest answer is to use the live interface in Place ID 136398881015015 and record only the commands it displays. Do not paste commands from Adonis, HD Admin, Kohl’s Admin, or another SAE experience into a guide for this game.
The title gives players a reason to expect admin tools. It still says nothing about syntax, effects, prices, cooldowns, targets, or persistence. Start with a dated status page. Add a command to the index only after you have checked it inside this exact game.
Current-status note: no exact command list was available in the public game information checked on September 14, 2026.
Build the command index from the live UI
Open the current panel if your account has a visible route to it. Before activating anything, create one row per displayed command.
| Command field | Required entry |
|---|---|
| Display name | Copy exact capitalization and punctuation |
| Input method | Button, text entry, selector, or another visible control |
| Target scope | Self, selected player, named player, or server option |
| Stated effect | Use the interface wording before testing the result |
| Cost | Cash, Robux, item, or no visible cost |
| Limit | Visible timer, disabled state, count, or no displayed limit |
| Confirmation | Exact warning and available cancel option |
| Immediate result | What changed right after activation |
| Persistence | Result after death, rejoin, and server switch |
| Checked on | Date, device, and public or private server |
Do not merge rows just because two labels sound similar. Separate entries make it possible to update one command without rewriting the entire page.
A safe command-testing order
Test the least risky controls first. Stop before anything that could spend currency, affect someone who has not agreed, or wipe progress.
1. Read-only controls
Start with filters, tabs, search boxes, target selectors, and information panels. Confirm how commands are grouped and whether selecting a target activates anything by itself.
2. Reversible self-target actions
If a command is clearly self-targeted and harmless, capture your baseline first. Record location, cash, $ / second, held object, and visible status. Activate the command once, then compare the same fields.
3. Consenting-player tests
Use a friend who agrees to the test. Both players should capture before and after states. Confirm whether the target sees a warning, can refuse, or can undo the effect.
4. Server-wide or destructive controls
Do not test these casually. A label that suggests kicking, resetting, deleting, changing the environment, or affecting the whole server needs a controlled session and a clear recovery plan.
Distinguish a button from a typed command
Players often use “command” for every admin action, but the interface can matter:
- A button action can work without a chat prefix or typed syntax.
- A text command needs exact characters, spaces, target format, and capitalization rules.
- A targeted action can require a player selection before you press the control.
- A toggle can stay active until you switch it off, die, or leave the session.
- A server setting can affect everyone, so do not test it like a personal tool.
Record the input type before describing syntax. Never invent a prefix because it is common in other Roblox admin products.
How to confirm what a command actually changed
Change one thing at a time. For an income action, keep the object setup and server fixed, then capture cash and $ / second before and after one activation. Test movement on the same route and device. When an avatar changes, record the target and duration without assuming that its stats changed too.
Repeat a safe test once. A result that happens only once could come from another player, a server event, a delayed reward, or a normal tycoon update. Two controlled observations are much stronger than a memorable single moment.
Signs that a command entry is not ready to publish
Hold the entry back when any of these conditions apply:
- the label came from a different experience;
- the target was not recorded;
- several actions ran at the same time;
- the result was observed only after switching servers;
- a cost changed but the starting balance was not captured;
- the tester cannot distinguish a timer from network delay;
- the command worked for one account but access conditions were not checked;
- the screenshot omits the experience title or Place ID.
A shorter verified list is more useful than a large list that sends players toward controls that do not exist.
Keep the page current
Admin systems can change quickly. Put a checked date beside the command table as well as at the top of the article. If a command changes, move the old entry into a dated note and keep the main instructions current.
Check the experience page and the live panel again after a Roblox update, a new game thumbnail, a changed interface, or repeated player reports that a label no longer exists.
FAQ
What are the current INFs ADMINS in SAE admin commands?
No exact public list is verified. Open the live interface in Place ID 136398881015015 and copy only the labels shown there before testing any action.
Does the game use a chat prefix for commands?
That is not documented. Do not assume a prefix from another admin system; check whether the live game uses buttons, text input, target selectors, or a combination.
Can commands change money or $ per second?
No such effect is confirmed. Capture both values before and after one clearly labeled, safe action if the live panel offers an economy-related control.
Are commands permanent after rejoining?
Persistence is unknown. For a harmless self-targeted effect, compare the state before activation, after activation, after death, after rejoining, and after changing servers.
Why are commands from other Roblox admin games excluded?
Different experiences can use different scripts, labels, permissions, and effects. Matching names do not prove that a command exists or behaves the same here.