Color theme

Moderation

Eranio

Moderation

Manage bans and mutes, with reason, duration and the responsible admin.


Overview

Three figures sit at the top: Banned players, Muted and Known players. Below are two tabs, Bans and Mutes, each with its own table and search field (player name, reason, responsible admin). Both tables refresh every 30 seconds.

Action Permission
View the lists hytale-admin.moderation-read
Ban, unban, mute, unmute hytale-admin.moderation-manage

In every form the player is picked from the list of known players (with search), not typed by hand.


Bans

The table shows avatar, player, type (Permanent in red, otherwise time limited), reason, responsible admin and time for every ban.

Data source

  1. First the bans.json file on the server, read through Pelican's file interface
  2. Otherwise the Java mod's API

Ban a player

Ban Player asks for the player and an optional reason.

Detail Value
API POST /api/bans
Success ":player has been banned"
Error "Failed to ban player"
Logged as server:hytale-admin.ban-player

Lift a ban

Unban asks for confirmation. The plugin first removes the entry directly from bans.json and only calls the API (DELETE /api/bans/{name}) when that does not work.

Detail Value
Success ":player has been unbanned"
Error "Failed to unban player"

Mutes

The table shows avatar, player, duration (time left such as "in 25 minutes", Expired in grey or Permanent in red), reason, responsible admin and time for every mute.

Mute a player

Mute Player asks for the player, Duration (minutes) and an optional reason. An empty duration means permanent.

Detail Value
API POST /api/mutes with player, reason, muted_by, duration_minutes
Success ":player has been muted"
Error "Failed to mute player"

The duration is in minutes: 60 is one hour, 1440 one day.

Lift a mute

Unmute asks for confirmation (DELETE /api/mutes/{player}).

Detail Value
Success ":player has been unmuted"
Error "Failed to unmute player"

UUID to name

Hytale stores bans by UUID. The panel shows the player name instead and looks it up in:

  1. known_players.json
  2. whitelist.json

If no name is found, the UUID is shown.


Troubleshooting

Ban list does not load

  • bans.json only exists after the first ban
  • Pelican's file interface cannot read the file, check file permissions
  • The API does not answer either, check the Java mod and the connection

"Failed to ban player"

  • Connection to the Java mod lost, check the status on the dashboard

Mute lasts the wrong time

  • The duration is in minutes, 60 is one hour
  • The server time zone may differ from the panel's

Ban shows a UUID instead of a name

  • The player is neither in known_players.json nor in whitelist.json
  • The panel picks up new players when the dashboard or the players page is opened (at most every five minutes)