HBL Plugin checks players on join via hytalebanlist.org, instantly blocks active bans, and gives staff /ban, /unban, /warning, /checkbans, and /hbl import with local queue + auto-sync local fallback when API limits are hit. Staff logins too!
Globally centralized moderation checks for Hytale servers with optional shared-ban enforcement, local warnings, and branded appeals pipeline & Staff Logins.
Stop known hackers, griefers and bad actors with ease.
Run /hbl auth and use the magic link provided. That's it. Your dashboard is live and your server is protected from known bad actors.
\\\*
config.json/hbl importIt is recommended to disable overlapping native moderation features in other installed mods.
Server/whitelist.json) that allows players immediately and skips API checks./ban, /unban, /warning) registered by the plugin.hytalebanlist.org.synced: false) with automatic retry sync at 00:01 UTC.config.json fields| Field | Type | Default | What it does |
|---|---|---|---|
| <code>api.key</code> | string | <code>"YOURAPIKEY_HERE"</code> | API key from Hytale Ban List dashboard. |
| <code>messages.kickMessage</code> | string | Includes <code>{reason}</code>, <code>{expires}</code>, <code>{appealUrl}</code> | Message shown when a player is denied. |
| <code>moderation.warningThreshold</code> | number | <code>3</code> | Auto-ban after this many warnings. |
| <code>moderation.defaultBanDuration</code> | string | <code>"perm"</code> | Default duration when <code>/ban</code> is used without time. |
| <code>general.locale</code> | string | <code>"en"</code> | Locale filename to load from <code>HytaleBanList/locales</code>. |
| <code>general.replaceNativeBanCommands</code> | boolean | <code>true</code> | Replaces native <code>/ban</code> and <code>/unban</code> with plugin versions. |
Use these for /ban and defaultBanDuration:
s secondsm minutesh hoursd daysw weeksmo months (~30d)y years (~365d)perm permanentExamples: 30m, 2h, 7d, 2w, 1mo, 1y, perm
/hblSubcommands:
/hbl auth → returns magic link for server setup/hbl reload → reload config and locale/hbl ban <player> [duration] [reason]/hbl unban <player>/hbl warn <player> [reason]/hbl checkbans/hbl import/ban <player> [duration] [reason]/unban <player>/warn <player> [reason]/checkbans/hbl help preview
[HytaleBanList] Help
/ban {player} {time} {reason} | /hbl ban {player} {time} {reason}
/unban {player} | /hbl unban {player}
/warning {player} {reason} | /hbl warn {player} {reason}
/hbl checkbans | /checkbans
/hbl import (imports from Hytale bans.json)
/hbl auth | /hbl reload
time: 30m 2h 7d 2w 1mo 1y permColor key in game output: red = ban, green = unban, yellow = header/warn/time, cyan = utility commands.
hytalebanlist.authhytalebanlist.reloadhytalebanlist.banhytalebanlist.unbanhytalebanlist.warninghytalebanlist.checkbanshytalebanlist.importLocalisation is fully optional but supported.
en.json locale.<your-locale>.json inside your plugin locale folder."locale": "<your-locale>" in config.json./hbl reload.If a custom locale is missing/invalid, the plugin falls back to bundled English.
/ban.When API limit is reached:
/ban still applies locally and disconnects immediately.bans.json with "synced": false.00:01 UTC."synced": true./warn.warningThreshold, plugin auto-submits a permanent ban.Global/shared-ban behavior is controlled by your Hytale Ban List server-side settings (dashboard/API policy), while this plugin enforces the ban-check response it receives.
In practice:
If API usage is exhausted (for example before reset at 00:00 UTC):
hytalebanlist.org to increase limit./checkbans is skipped while limited and shows a rate-limit message.After reset:
synced: false) are retried automatically at 00:01 UTC.HytaleBanList.org supports custom moderation portals (ban list, lookup, appeals) on your own subdomain with a paid plan.
Example portal URLs:
https://bans.yourserver.com/https://bans.yourserver.com/searchhttps://bans.yourserver.com/appeal/:banIdAdd both records at your DNS provider:
bans.yourserver.com (or your chosen subdomain)appeals.hytalebanlist.org_hytale-verify.bans.yourserver.comhbl_verify_<token>Then verify DNS in dashboard once records propagate.
After setup, verify these quickly:
/hbl reload succeeds./ban and /warn permissions are assigned to staff roles.{reason}, {expires}, {appealUrl}).
0 Comments