Which 🍪 cookies would you like to allow?

You decide which services we may enable for analytics, personalization, and external content.

We use cookies and similar technologies on our website to personalize content, embed external media, and better understand how individual areas are used.

Necessary cookies

These entries support essential functions such as security, stability, and form processing.

Optional sections

AnalyticsMarketingPersonalizationExternal media

Your data may be processed with your consent or on the basis of legitimate interests. In the cookie settings, you can reject or explicitly allow each optional category.

Some services process personal data in third countries. By consenting, you also agree to this transfer. You can find more information in our Privacy Policy.

You can reopen and change your selection at any time. · 1.0.2

Server & Administration

/ban

Ban a player

Accepts additional words after the arguments.

Spelling

/ban <player>

Main commandthe command name that starts it all
Requiredrequired, in a fixed order

Arguments

Argument	Type	Type	Description
`player`	Required	Player UUID/Username (with lookup) A player UUID or username. If not found locally, performs a remote lookup via the Profile Service.	The player to ban (username or UUID)

Permissions

Permission: hytale.accesscontrolmodule.command.ban

The groups build on one another: Adventurer, Builder, WorldEditor, ServerEditor, Admin. Higher groups inherit the permissions of lower ones; new players are Adventurers, and admins (OP) can do everything.

Back to command reference

/ban — Hytale command reference | ZAP-Hosting