-
-
How it works
Try this product in game with a hosted Minecraft server!- Click 'Generate test server'
- Join the provided IP address
- Try out the product for up to 30 minutes
- Stop the server when you're done
Requesting a test server will duplicate the original files and provide you a new server for you to join and experiment with for up to 30 minutes. Any changes you make will not be saved so feel free to play around!
There are no limits to the number of servers you may start, but you can only have one test server active at a time. You must stop any active test servers in order to start up a new one.Features
- Completely free
- Instant setup
- Full operator permissions
- Invite friends
- No usage limits
Testing servers provided by PebbleHost.
Visit PebbleHost.com
Punishments is a plugin designed to simplify managing player punishments in Litebans by providing a more user-friendly graphical interface.
- /punish
The punish command is designed to punish players using a user-interface approach and automatically assigning ban lengths depending on the player's current history.
You can punish a user without using the interface by providing a few arguments.
- /history
The history command is designed for staff members to view a player's history in a user-interface environment.
- /record
The record command is very similar to the history command but accessible to all players; you can only view your punishment history.
- /staffhistory
The staff history command is designed for staff members to view the history of punishments they have done over time.
- /staffleaderboard
The staff leaderboard command is a new system, which, in short, is a leaderboard system to display staff members according to their total punishments. This can be disabled.
- /punishreload
A simple command designed to reload the configuration files in-game.

- /punish
The punish command is designed to punish players using a user-interface approach and automatically assigning ban lengths depending on the player's current history.
You can punish a user without using the interface by providing a few arguments.
- /history
The history command is designed for staff members to view a player's history in a user-interface environment.
- /record
The record command is very similar to the history command but accessible to all players; you can only view your punishment history.
- /staffhistory
The staff history command is designed for staff members to view the history of punishments they have done over time.
- /staffleaderboard
The staff leaderboard command is a new system, which, in short, is a leaderboard system to display staff members according to their total punishments. This can be disabled.
- /punishreload
A simple command designed to reload the configuration files in-game.
YAML:
# --------------------------------------------------------
# Punishments Configuration
# Useful Resources:
# * Discord: https://dsc.gg/negative-games
# * MiniMessage Format: https://docs.advntr.dev/minimessage/format.html
# * MiniMessage Web UI: https://webui.advntr.dev/
# --------------------------------------------------------
# When true, the plugin will disable unnecessary logs to the console.
disable-unnecessary-logs: false
# The interval in seconds in which the cache is synchronized with the database.
# In lamen's terms, this is the interval that the plugin will check the database for new
# or updated punishments and then store them locally.
cache-sync-interval: 5
# When true, the /record command is enabled for all players to use.
record-command-enabled: true
# Whether to use a categorized record menu or not.
# If set to true, the record menu will be categorized
# by punishment type (e.g. mutes, bans, warns) in their own
# dedicated submenus, similar to the /history command.
#
# If set to false, the record menu will display all punishments
# in a single menu.
record-menu-categorized: true
# Staff Leaderboard Configuration
staff-leaderboard:
# When true, the staff leaderboard system is enabled.
enabled: true
# The interval in seconds in which the staff leaderboard cache is synchronized with the database.
# In lamen's terms, this is the interval that the plugin will check the database for new
# or updated staff leaderboard data and then store it locally.
cache-sync-interval: 30
# Note Configuration
notes:
# When true, the note system is enabled.
enabled: true
# When true, the note database system will use an external database instead of the default SQLite database.
use-external-database: false
# External Database Information
database:
host: localhost
port: 3306
database: punishments
username: root
password: password
# Punishments
punishments:
Hacking:
reason: Hacking
filter-revoked-punishments: false
forgiveness: 100d
icon:
position: 10
name: <red>Hacking
material: BOOK
lore:
- ' '
- '<white>Violation #1: <yellow>7 days <red>(BAN)'
- '<white>Violation #2: <yellow>30 days <red>(BAN)'
- '<white>Violation #3: <yellow>Permanent <red>(IP BAN)'
- ' '
- '<white>Total Punishments: <yellow>%total%'
ladder:
FIRST:
length: 30d
category: BAN
force-silent: true
ip: false
commands:
- lp user %player% parent remove VIP
# Authors: ericlmao
YAML:
SPECIFY_PUNISHMENT:
- <red><bold>ERROR!</bold> <gray>Please specify a punishment!
INVALID_PUNISHMENT:
- <red><bold>ERROR!</bold> <gray>The punishment of '<red>%argument%</red>' cannot
be found.
CANNOT_PUNISH_SELF:
- <red><bold>ERROR!</bold> <gray>You cannot punish yourself!
STAFF_HISTORY_MISSING_PROFILES:
- <gray><i>Some records are missing critical data to be displayed, so they have been
omitted.
RELOAD:
- <green><bold>SUCCESS!</bold> <gray>Reloaded configuration files!
NOTE_NOTICE_TOGGLE_ON:
- <green><bold>SUCCESS!</bold> <gray>You have toggled note notices <dark_green><bold>ON</bold></dark_green>!
NOTE_NOTICE_TOGGLE_OFF:
- <green><bold>SUCCESS!</bold> <gray>You have toggled note notices <red><bold>OFF</bold></red>!
NOTE_NOTICE:
- <aqua>[Alert] <gray>Player <aqua>%player%</aqua> has joined and has <aqua>%amount%</aqua>
notes (<red>%severe%</red> severe).
NOTE_CREATE_PROMPT:
- <aqua>[Alert] <gray>Please enter the note you would like to attach to this user.
- <gray><i><click:suggest_command:'cancel'>Click this message or type <red>cancel</red>
to cancel!</click>
NOTE_CREATE_CANCELLED:
- <red><bold>CANCELLED!</bold> <gray>You have canceled the note creation process!
NOTE_CREATED:
- <green><bold>SUCCESS!</bold> <gray>You have created a note for <aqua>%player%</aqua>!
NOTE_EDIT_PROMPT:
- <aqua>[Alert] <gray>Please enter the new content of the note you would like to change!
- <gray><i><click:run_command:'cancel'>Click this message or type <red>cancel</red>
to cancel!</click>
NOTE_EDIT_CANCELLED:
- <red><bold>CANCELLED!</bold> <gray>You have cancelled the note editorial process!
NOTE_EDITED:
- <green><bold>SUCCESS!</bold> <gray>You have edited the content for the note!
NOTE_DELETE_CONFIRMED:
- <aqua>[Alert] <gray>You have successfully deleted the note.