Tower of Hell private-server commands help owners manage practice and events. The official game description confirms owner settings for skipping, tower size, and shop locking, but it does not publish a complete command grammar. The syntax below is community reported and must be tested in the current live server.
Reported command lookup
/skip
Reported to skip the current tower or round.
Verify: confirmation and effect before repeating.
/setlength
Reported to change tower size with an argument.
Verify: accepted range and when it takes effect.
/lockshop
Reported to prevent shop use.
Verify: owner status and current round behavior.
/unlockshop
Reported to restore shop use.
Verify: confirmation after a locked session.
/kick
Reported moderation command for removing a player.
Verify: exact player argument and permissions.
/serverban
Reported stronger server moderation action.
Verify: scope, duration, and reversal path.
/serverinfo
Reported to show current server information.
Verify: fields and privacy before sharing output.
/ttoh
Reported in connection with THE Tower of Hell.
Verify: current access, place, and result.
This lookup deliberately omits invented arguments. Read the live help, interface, or response for the exact format.
Test a command safely
Use a private server you own or are authorized to manage. Record the current tower and settings. Enter one command from a safe lobby area, then wait for a visible response. Confirm the result before testing another. Restore the original state when finished.
If chat displays the text publicly but nothing changes, do not spam it. The syntax may be stale, the feature may have moved into settings, or the account may lack permission.
Prefer visible settings when available
The official description explicitly directs VIP owners to settings for skip, size, and shop lock. A menu label is less ambiguous than a copied command. Use the current interface when it offers the same action, and let the game validate its allowed values.
Commands remain useful for quick control only after their current behavior is confirmed.
Use moderation commands proportionally
Explain server rules before an event. Use kick for immediate disruption when appropriate, and verify what serverban means in the current version before applying it. Record the player name and reason privately. Do not publish personal information or turn game moderation into off-platform harassment.
Roblox’s platform-level reporting and blocking tools remain separate from a game-server command.
Keep commands separate from codes
A slash command is an owner or server action, not a reward code. It does not grant free coins, effects, Membership, or gamepasses merely because a search page labels it a “code.” The codes page explains why no current promo list is published.
Never run an executor or paste browser-console code to unlock owner actions. Legitimate tools work through the official client and current permissions.
Troubleshoot no response
Confirm the experience, private-server ownership, spelling, argument format, and current chat behavior. Check whether the action moved to a settings control. Rejoin the official server if the client is out of sync. Search for a current full-session demonstration rather than trusting a cropped command table.
For /ttoh, verify that any destination belongs to official Universe 703124385; the current official THE place uses Place ID 94971861814985.
Run a small command rehearsal
Create a low-stakes session before hosting an event. Use /serverinfo first if the current server accepts it, then try one reversible shop or tower setting. Ask a second player to confirm what changed from their client. Restore the setting and confirm the restoration too. This rehearsal catches permission, chat, and application-timing differences without destroying a serious climb.
Test moderation only with a consenting helper or when a real rule violation requires it. Do not experiment with a ban command on an uninvolved player. If the server provides no visible reversal path, learn that path through current official controls before using the action.
Keep a short owner note with the exact accepted input, response, effect, and check date. Replace it when the game changes rather than layering newer guesses over older syntax.
Command-session checklist
- Owner or authorized role confirmed.
- Original state recorded.
- Current visible settings checked first.
- One command entered once.
- Live response and effect observed.
- Arguments not guessed from an old guide.
- Moderation reason documented.
- Shop and tower state restored afterward.
- No scripts, executors, credentials, or off-platform tools used.
Sources and confidence
Skip, size, and shop-lock responsibilities are supported by the official game description checked August 23, 2026. Every exact slash command on this page is community documented, not a guaranteed first-party command reference. Live permissions, syntax, responses, and effects control.