No command limit or cooldown is publicly confirmed
There is no published table of INFs ADMINS in SAE admin command limits on the current Roblox listing. Do not assume that an action is unlimited because its button is visible, and do not borrow cooldown numbers from another Roblox admin game. Check the exact live interface at Place ID 136398881015015 and record one variable at a time.
A limit can show up as a timer, a disabled button, a price, a target restriction, a per-life allowance, or a server rule. Sometimes the command is fine and the target failed to load. Test each possibility on its own.
Current-status note: no exact cooldown, cost, use count, or target restriction was published in the game information checked on September 14, 2026.
Start with a safe baseline
Before you press a command control, take a quick snapshot of anything that could change:
- command label and panel section;
- selected target;
- visible cash and
$ / second; - any timer, count, or disabled state;
- held object and player location;
- server type, device, and time;
- warning dialog and cancel option.
Use a harmless self-target action if the panel labels one clearly. Never start with a server-wide action, a kick or reset control, a purchase, or anything aimed at a stranger.
Use this limit test matrix
| Test | Keep fixed | Change | Record |
|---|---|---|---|
| Immediate repeat | Account, server, target | Press the same action twice | Timer, message, disabled state, second result |
| Short wait | Account, server, target | Wait a measured interval | Exact time when control returns |
| Target change | Account, server, command | Select a consenting second player | Whether the restriction follows the command or target |
| Death check | Account and server | Reset only when safe | Whether access, timer, and effect reset |
| Rejoin check | Account | Rejoin the same experience | Whether the limit persists across sessions |
| Server check | Account and device | Join a different public server | Whether state is account-based or server-based |
Run one row at a time. Change the target, server, and device together and you will have no idea which one triggered the rule.
Tell a real cooldown from a delay
A visible countdown with a clear unit is the strongest sign of a cooldown. Copy the displayed start value and note when the action becomes selectable again. If there is no timer, measure from activation to the first successful repeat and run the same safe test twice.
One failed click does not prove there is a cooldown. Check these points first:
- Was the target still valid and in the server?
- Did the panel remain connected and responsive?
- Did the action show a cost you could not pay?
- Did the first effect need to end before another activation?
- Did a warning or confirmation remain open?
If the interface gives no message, label the result repeat blocked; reason not displayed rather than inventing a timer.
Record costs without spending carelessly
Some controls can display cash, Robux, item, or use-count requirements. Capture the current amount and the stated price before confirming anything. For Robux prompts, use the official Roblox purchase window and read the current product description. Never follow an external payment link.
If a harmless action consumes in-game cash, compare the balance immediately before and after exactly one use. Do not infer a fixed cost from a session where normal tycoon income continued changing the balance.
Check target and permission limits
A command that works on self does not automatically work on another player. With a consenting friend, record the target selector before activation and capture both players’ results. Look for:
- self-only labels;
- owner, admin, or role messages;
- protected-player messages;
- server-wide target options;
- distance or location restrictions;
- confirmation shown to the target;
- an undo or recovery control.
Stop if the target cannot consent or the effect could cause progress loss. A complete guide does not require unsafe testing.
How to publish a limit accurately
A finished table row needs the checked date and device, plus the server type, exact label, target, visible cost, measured cooldown, repeat count, and persistence result. Write not displayed when the UI gives no value. Use not tested when the check would be unsafe.
Avoid words such as unlimited, permanent, or no cooldown unless repeated live checks and the interface both support that conclusion. Even then, add the checked date because limits can change.
Common testing errors
Network lag can look like a cooldown. Wait for the panel to respond, then repeat the same controlled action.
Passive income can hide the real cost. Record $ / second and the exact timing.
A protected player can make a working command look blocked for everyone. Stick to one target while testing.
Death does not automatically clear every state. Check death, rejoin, and server change separately.
A blank field is not zero. If there is no displayed timer, do not report a zero-second cooldown.
FAQ
Are the admin commands unlimited in INFs ADMINS in SAE?
That is not confirmed. Check the live control for a timer, cost, disabled state, count, or target message and record the result with a date.
How do I measure a command cooldown?
Use one harmless action on the same target, start timing at activation, and note the first successful repeat. Run the test twice before publishing a value.
Does rejoining reset command limits?
No reset rule is documented. Compare the visible state before leaving, after rejoining, and after joining a different public server.
Can limits be different for each player?
Yes, that is a condition worth checking, but it is not confirmed here. Compare consenting accounts while keeping the server, device, command, and target setup consistent.
Is a missing timer proof that there is no cooldown?
No. The interface can enforce a restriction without displaying a countdown. Record the observed repeat behavior and avoid assigning a numeric value without measurement.