Do not test player effects on strangers
No exact INFs ADMINS in SAE admin player effects are documented on the current Roblox listing. The game supports up to seven players per server, so any target-based admin tool needs a consent-first test. Do not assume that the title grants permission to disrupt another player’s session.
Only test an action when you can read its label, see its target, and know how to recover. Start on your own character. If the check needs a second player, ask a friend and explain the action before you press it.
Current-status note: no player-targeted effect, protection rule, or recovery behavior was publicly confirmed as of September 14, 2026.
Separate target scope from effect type
Before you activate anything, look at the selected target. Check it again even if you chose the same player a moment ago.
| Target scope | What to verify | Safe starting rule |
|---|---|---|
| Self | Your own name or a self label is selected | Use only a clearly reversible action |
| One player | A consenting player’s name is selected | Both players capture before and after states |
| Multiple players | More than one target is shown | Do not test in a public server |
| Whole server | An all-player or server label is shown | Stop unless you control the session and recovery |
| Unclear | No selected target is visible | Cancel and do not activate |
A control can remember the previous target after the panel closes. Recheck the selected name every time rather than assuming it reset to self.
Use a consent-first test protocol
Step 1: agree on the test
Tell the other player the displayed action label, what you plan to watch, and how the test ends. Either player should be able to cancel before activation.
Step 2: capture both baselines
Both players should record their position, avatar state, cash, $ / second, held object, and any visible status. Leave irrelevant fields alone. Extra changes only muddy the result.
Step 3: activate once
Read the selected target one last time, then press the control once. Save any confirmation, error, timer, or cost that shows up. Wait until the result ends before trying another command.
Step 4: record the immediate result
Write down the change on each screen. A different-looking avatar does not prove its speed, income, inventory, or health changed too.
Step 5: recover before continuing
Use an undo button or toggle only when the label is unambiguous. Otherwise, wait. Reset or rejoin only after the other player accepts the risk and saves their current state.
Categories to check without assuming they exist
Players will want the areas below checked. They are categories for a test sheet, not a confirmed feature list:
- movement or position;
- avatar appearance or size;
- teleport or flight-style controls;
- cash or income-rate changes;
- object spawning or removal;
- environment or event changes;
- player removal or access restrictions.
Use these as headings in a test sheet, then fill a row only when the exact live interface displays a matching control. Do not turn an empty heading into a command name.
Check whether the target can protect themselves
A useful safety guide records more than the visible effect. Ask:
- Does the target receive a warning or confirmation?
- Can the target decline before activation?
- Is there a shield, opt-out, protected role, or cooldown message?
- Can the target undo the effect from their own interface?
- Does death clear the effect?
- Does rejoining clear it without changing saved progress?
- Can the same action be repeated immediately?
Record not shown when the interface provides no protection message. Do not claim that no protection exists after one test.
Track duration and persistence separately
Duration is how long an effect lasts in the current session. Persistence is whether it remains after a life or session boundary. Measure them with separate checks.
| Boundary | Record |
|---|---|
| Ten seconds after activation | Whether the visible result remains |
| Effect’s displayed timer end | Whether the original state returns |
| Player death | Whether the result clears or changes |
| Same-server respawn | Whether panel access and state return |
| Rejoin | Whether the effect or altered value remains |
| Different server | Whether the state follows the account |
Do not risk saved progress to complete the table. Mark an unsafe check as not tested and explain why in one sentence.
Avoid false cause-and-effect claims
The game is listed as a tycoon, and its official artwork shows a Most $/s comparison. Normal income can keep changing during an admin test. Note the time and starting values so you do not mistake passive progress for a command effect.
Other players or server events can also change the scene. A clean test uses one action, one target, a short observation window, and a repeated safe result. If the change cannot be reproduced, publish it as an unresolved observation rather than a working effect.
FAQ
Can admins target other players in INFs ADMINS in SAE?
That is not publicly confirmed. Check the live panel for a target selector and test only with a consenting player in a controlled session.
Which player effects are available?
No exact list is verified. Record only controls displayed in this experience and keep movement, avatar, economy, object, and server categories empty until a matching control is observed.
Can a player refuse an admin effect?
No protection rule is documented. Capture any target warning, confirmation, shield, opt-out, protected-role, or cooldown message before activation.
Do player effects survive rejoining?
Persistence is unknown. Test a harmless effect across its timer, death, same-server respawn, rejoin, and a different server as separate steps.
What if the selected target is unclear?
Cancel the action. Reopen the panel, confirm the exact target name or self label, and do not activate a multiplayer control without a visible selection.