Native Minecraft Version:
1.15
Tested Minecraft Versions:
English by default, all messages configurable
Donation Link:
https://www.paypal.me/dart2112
NOTE: The plugin is currently undergoing a rewrite to bring it up to the latest LapisCore and LapisDatastore for a more robust plugin and an overall better experience for you guys. This does mean that some messages and text on this page will not match what is in the latest version until the final release
- Temporary and permanent Bans & IP Bans
- Shadow bans
This is a feature that allows you to effectively ban a player without their knowledge, you can control what the player can do while shadow banned. By default the player cannot break place or interact with blocks or items, any chat messages they send will only be visible to them and console and any items they drop will be destroyed.
- Mutes and Temp mutes
There are configurable options for mutes that allow you to ban any chat commands your server may have like /tell so that a muted player cannot communicate with anyone, even outside of global chat
- Warnings and configurable punishments for multiple warnings
This means you can just give moderators the permission to warn people and let the automated system deal with other punishments like kicks and temp bans
- Multiple time units for temporary punishments
If you want to ban someone for 1 year and 1 month you can, the plugin will automatically detect all integers and time units when they are in the correct part of the command and add then to the duration of the punishment
- View the full punishment history for a player or punishments handed down by a staff member including any past punishments
This means you can see how many times a player has been muted or kicked, the staff history command also allows you to see how often your staff are handing down punishments
- View the active punishments for any player
The history command shows all punishments, past and present. The player command can be used to just see the currertly active punishments.
- Rollback of punishments handled down by a staff member before or after a certain amount of time
If you have a rouge staff member or a player who has gotten staff permissions they might have banned a lot of people and it would be a real pain to go through and unban them all. but with the lapisbans rollback command you can specify a time and all the punishments before or after that time will be removed. e.g. "/lapisbans rollback dart2112 before 1 week" would remove all punishments I have given that are older than a week. you can also say after for any punishments that are newer
- Remove warnings with a time restraint.
e.g. remove all warnings given before 2 weeks ago
This works in the same way as staff rollback but will only remove warnings from players
- Advanced player data storage with the options of H2 local
database, MySQL or SQLite
H2 is the default as it is the fastest and doesn't require any configuration on your part
MySQL is preferred particularly on a network
You also have the option of SQLite
- The ability to disable any command
want another plugin to handle the /ban command? simply add the command to the disabled command list in the configuration
- Entirely custom permissions system
No need to remember 30 different permissions, just make a few in the configuration and give each player one permission
- Every message ever sent to a player can be modified
All messages sent to players (excluding plugin info sent by /lapisbans) are customizable in the messages.yml
- Automatic reloading of configurations
If you make an edit to the config.yml or messages.yml file it will be loaded into the plugin and anything that can be updated live will be. This applies to all messages and some config.yml values
- Importing of punishments from other ban plugins
Currently you can use "/lapisbans import advancedban" to retrieve all punishments from Advanced Ban and add them to Lapis Bans, you can also import from vanilla, essentials, MaxBans and MaxBansPlus
- Update notifications
When there is an update on spigot you will receive a notification in console letting you know what version you are on and what the latest version is
If there is no update you will still receive a message letting you know that there was no update available
/lapisbans [player|import|rollback|help]:
The permissions system in this plugin is the LapisCore Permissions system. You can find info on how to set up and use it at the wiki below
https://github.com/LapisPlugins/LapisCore/wiki/Lapis-Permissions
The API currently allows you to get all punishments for a player and apply punishments to a player. get the API and the Java Docs on GitHub at https://github.com/Dart2112/LapisBansAPI
This plugin can collect data about how many players and servers are using it and what specifications they have. This data is used to see what the needs of the community are and what demographic I am coding for
https://bstats.org/plugin/bukkit/LapisBans
- Hiding shadow banned players from non-shadow banned players
- Got anything you would like to see, let me know!
1.15
Tested Minecraft Versions:
- 1.15
English by default, all messages configurable
Donation Link:
https://www.paypal.me/dart2112
NOTE: The plugin is currently undergoing a rewrite to bring it up to the latest LapisCore and LapisDatastore for a more robust plugin and an overall better experience for you guys. This does mean that some messages and text on this page will not match what is in the latest version until the final release
- Temporary and permanent Bans & IP Bans
- Shadow bans
This is a feature that allows you to effectively ban a player without their knowledge, you can control what the player can do while shadow banned. By default the player cannot break place or interact with blocks or items, any chat messages they send will only be visible to them and console and any items they drop will be destroyed.
- Mutes and Temp mutes
There are configurable options for mutes that allow you to ban any chat commands your server may have like /tell so that a muted player cannot communicate with anyone, even outside of global chat
- Warnings and configurable punishments for multiple warnings
This means you can just give moderators the permission to warn people and let the automated system deal with other punishments like kicks and temp bans
- Multiple time units for temporary punishments
If you want to ban someone for 1 year and 1 month you can, the plugin will automatically detect all integers and time units when they are in the correct part of the command and add then to the duration of the punishment
- View the full punishment history for a player or punishments handed down by a staff member including any past punishments
This means you can see how many times a player has been muted or kicked, the staff history command also allows you to see how often your staff are handing down punishments
- View the active punishments for any player
The history command shows all punishments, past and present. The player command can be used to just see the currertly active punishments.
- Rollback of punishments handled down by a staff member before or after a certain amount of time
If you have a rouge staff member or a player who has gotten staff permissions they might have banned a lot of people and it would be a real pain to go through and unban them all. but with the lapisbans rollback command you can specify a time and all the punishments before or after that time will be removed. e.g. "/lapisbans rollback dart2112 before 1 week" would remove all punishments I have given that are older than a week. you can also say after for any punishments that are newer
- Remove warnings with a time restraint.
e.g. remove all warnings given before 2 weeks ago
This works in the same way as staff rollback but will only remove warnings from players
- Advanced player data storage with the options of H2 local
database, MySQL or SQLite
H2 is the default as it is the fastest and doesn't require any configuration on your part
MySQL is preferred particularly on a network
You also have the option of SQLite
- The ability to disable any command
want another plugin to handle the /ban command? simply add the command to the disabled command list in the configuration
- Entirely custom permissions system
No need to remember 30 different permissions, just make a few in the configuration and give each player one permission
- Every message ever sent to a player can be modified
All messages sent to players (excluding plugin info sent by /lapisbans) are customizable in the messages.yml
- Automatic reloading of configurations
If you make an edit to the config.yml or messages.yml file it will be loaded into the plugin and anything that can be updated live will be. This applies to all messages and some config.yml values
- Importing of punishments from other ban plugins
Currently you can use "/lapisbans import advancedban" to retrieve all punishments from Advanced Ban and add them to Lapis Bans, you can also import from vanilla, essentials, MaxBans and MaxBansPlus
- Update notifications
When there is an update on spigot you will receive a notification in console letting you know what version you are on and what the latest version is
If there is no update you will still receive a message letting you know that there was no update available
/lapisbans [player|import|rollback|help]:
- without any arguments this command simply prints the plugin info including version and spigot link
- Player: the player command requires a username e.g. "/lapisbans player dart2112". This will show all active punishments for the given player
- Import: the import command requires a plugin name e.g. "/lapisbans import advancedban". this will import all punishments from the given plugin, currently it supports advancedban, Essentials, vanilla, MaxBans and MaxBansPlus.
- Rollback: the rollback command takes a staff members name and optionally [before|after] [time]. e.g. "/lapisbans rollback dart2112" will remove all punishments I have ever given. but "/lapisbans rollback dart2112 after 1 hour 30 minutes" will only delete punishments newer than an hour and a half
- Help: this command will display the help text for every lapisbans command, be warned that there are more messages then can fit on the screen so you will need to scroll
- The username must be of a player who has been on the serer before
- The time is made of 1 or more sets of integer and time unit e.g. "1 hour 30 minutes 5 seconds" please do not put and or anything else between the times or they wont be detected properly and will be included in the reason. if no time is given the ban will be permanent
- The reason can be as long as you like, you can include the -silent tag if you don't want the punishment to be broadcast to all players. the -silent tag will automatically me omitted from the reason message. For bans you can also include the -shadow tag if you want to shadow ban the player, this tag is also omitted from the reason message. If you do not provide a reason the default from the messages.yml will be used
- This command has an alias of /lapisbanshistory for servers who already have a /history command
- The username or IP address must be of a player who has played before, for IP address it must be of a player who has joined since the plugin was installed.
- This command will return a list of all punishments that have been applied to the given username or IP address, This will include any punishments that have expired or been removed
- The username must be of a player who has joined since Lapis Bans was installed since we use the username to lookup the players IP address
- For information about time, reason and tags please refer to the /ban command information above
- The username or IP address must be of a player who has joined since Lapis Bans was installed
- The command will return the IP address of the player if a username is given or the username(s) if an IP address is given
- The username must be of a player who has played before
- For information about reason and tags please refer to the /ban command and take note that the -shadow tag can only be used for bans
- the username must be of a player who has played before
- for information about time, reason and tags please refer to the /ban command and take note that the -shadow tag can only be used for bans
- A muted player cannot type in chat or use chat commands, the list of chat commands is contained in the config.yml and can be edited to have all chat commands on your server
- This command has an alias of /lapisbansstaffhistory for servers who already have /staffhistory command
- This command will show all punishments given by a player or console, use the name of console to see the punishments given by console or by the automated warning system
- the username or IP address must be of a player or IP address that is banned
- If you give a username then that user will be unbanned before they are un IP banned, if you wish to only remove an IP ban use /iplookup and unban the IP directly
- If you use a IP address then only the IP ban will be lifted
- the username given must be muted for this command to do anything
- The before and after time system is identical to that of the staff rollback command in /lapisbans, please refer to that for more information on how to define a time
- If no time is given then all warnings will be removed
- The reason and tags for this command work in the same way as the /ban command, please refer to it above for more information. Please note that the -shadow tag only works for bans
- In the config.yml you will find a warning commands list, the command will be run if the player has received the number of warnings stated at the start of the line. These don't have to be Lapis Bans commands, but they need to be usable from console as they are executed via the console. in the comment above the list there are some placeholders that you are free to use in any of the commands. if there is no command for the current number of warnings, no command will be run. try to add commands that can be used if the player is offline as the commands will be run regardless of if the player is currently online
- If you give a player a warning while they are offline, they will be alerted of the warnings that they have received when they next login
The permissions system in this plugin is the LapisCore Permissions system. You can find info on how to set up and use it at the wiki below
https://github.com/LapisPlugins/LapisCore/wiki/Lapis-Permissions
The API currently allows you to get all punishments for a player and apply punishments to a player. get the API and the Java Docs on GitHub at https://github.com/Dart2112/LapisBansAPI
This plugin can collect data about how many players and servers are using it and what specifications they have. This data is used to see what the needs of the community are and what demographic I am coding for
https://bstats.org/plugin/bukkit/LapisBans
- Hiding shadow banned players from non-shadow banned players
- Got anything you would like to see, let me know!