SimpleDeathBans
SimpleDeathBans
Important Notices
- Will be updated to use UUIDs instead of usernames soon. Please stand by.
- Version 1.5 adds support for third party ban conditions. View the 'Config Explanation' section for details.
General Information
On death, players are kicked from server, and ban is saved into a MySQL / SQLite database.
Saved information includes:
- Player Name
- Cause of death (if applicable)
- Entity caused by (if applicable)
- Date
- Active (defaults to 1)
When a player joins, their name is tested against active deaths. If they are dead / banned, they are kicked with a custom kick message.
The plugin doesn't actually do anything with saved information (apart from player name and date), however a web application is available if you wish to display death information on a website. The web app, written in PHP, can be found here https://github.com/Echo4190/SDB-Web-App/downloads. This web app is still being updated with various features.
Setup
- Simply place plugin into plugins folder and reload / restart server.
MySQL Setup
If you want to use a MySQL database instead of an SQLite database, simply change the 'driver' config option from 'sqlite' to 'mysql', and complete the mysql connection details.
Web App Setup
Download the compressed copy of the web app from the following link:
https://github.com/Echo4190/SDB-Web-App/downloads
You must be making use of a MySQL database in order to take advantage of this web app.
- Uncompress the files into your web directory. Your web server must support PHP with MySQL.
- Modify the 'config.php' file in the root directory with your MySQL connection details. You can also edit death messages that appear on the page.
You should now be able to view active deaths on the website. This web package is still being updated.
Default Configuration
kickmessage: You're Dead :( bantime: 0 dobans: true db: driver: sqlite mysql: username: uname password: pword host: localhost port: 3306 database: deathbans sqlite: file: plugins/SimpleDeathBans/simpledeathbans.sqlite thirdparty: Factions: enabled: false banatpower: -10
Config Explanation
- Kill message and database are self explanatory.
- Bantime is in minutes, and specifies how long a user will be unable to join the server for once they are killed. A bantime of 0 is a permanent ban (useful for if you want to reset all bans at the end of the month, by using '/deathbans reset')
- Dobans sets whether or not to actually ban players. If you simply want to use the plugin in conjunction with the web app for displaying deaths on a website without actually banning players, set this config value to false.
As of v1.5 there is support for third party ban conditions.
In order to utilize the conditional thirdparty banning, 'dobans' must be 'false' to disable the default ban handling (which is obviously ban on any death).
PM me for third party ban conditions for other plugins and I'll look into adding them.
Factions
- banatpower - When a players power level gets equal to or below this value, they are deathbanned.
Todo List
- Save players last words to database on death.
Commands
- /deathbans - List possible commands
- /deathbans reset - Set all deaths to inactive.
- /deathbans reload db - Reload deaths from MySQL database
- /deathbans reload config - Reload config file (which causes a database reload as well)
- /deathbans revive <player> - Set active deaths matching the player to inactive.
Permissions
- deathbans.invincible - Don't ban player on death. Helpful if you're admin, and want to.. administrate your server.
- deathbans.reset - Allow use of the '/deathbans reset' command
- deathbans.reload.database - Allow use of the '/deathbans reload db' command.
- deathbans.reload.config - Allow use of the '/deathbans reload config' command.
- deathbans.revive - Allow use of the '/deathbans revive' command.
External Information
- Y0urShad0vv has made an instructional youtube video for this plugin, available here: http://www.youtube.com/watch?v=Wka9RT3-T00
Famous Quotes
"I, am not a java god" ~ gv1222
Hey id be willing to pay u 30$ to fix this one minor problem with your plugin. I want to allow players to purchase revives on my server for 1$ and full revives for 5$ (Revive everyone whos dead so basically a /deathbans reset) however your plugin wont allow it. For one the /deathbans revive (name) must be lowercase for some reason so when they buy it and the command runs through buycraft it puts a capital on the capitalised letters causing the purchase not to work. Also the reset command requires a confirming command to be made right after meaning I cant allow them to buy that either. Please fix these 2 issues for me and I would happily pay u for it.
@buddhist09
Yes. Stand by
Any chance of updating this to uuid's?
Here is video tutorial
@magides
I just tested against the current version (1.5.1) and it appears to be working as intended.
Are you running an abnormal setup, or are there any errors in the console you can share?
for some reason, the 'banned' player is still able to join the server.
When they die, they are kicked instantly with the kick message - but after logging out and logging back in, they are given another chance ?
Is there a way where you can add permissions for this plugin? What I mean is possibly setting different deathban timers for different ranks. Like say I want regular players to have a 10min deathban, but VIP players have only a 5min deathban.
Thanks for the consideration! Will help out bunches!
Can you add automatic database reload to plugin ?
@gepardo43
I'll look into allowing users to customize these messages in the next version.
Can you add in next version translation of these messages:
"time until respawn"
"days"
"hours"
"minutes"
Thanks
@joshwenke
As in the user gets banned only when they die in a particular world?
Multi-world and individual world ban support! Pretty please? :)
Awesome update!
@ServerMineria
As discussed in PMs, thanks for pointing out this bug to me.
No, the plugin does not actively poll the database after it has initially loaded it. Any changes to the database will only be synchronized with the plugin after deathbans reload database is called. How you make this call (e.g, with a command scheduler) is up to you.
Nice plugin, but whenever i use reload database or reboot the server, doesn't matter if there's active=1; players are able to connect :x
using MySQL, didn't test with SQLite.
and is it dynamic, if my website edit the active column ? or should I use a command scheduler ?
thanks
How bout support for factions? Once reached -10/10 power you get banned for a set time?
@Banana937
It should be compatible. I'll compile it against the latest bukkit API to be sure.
Any chance of an update some time soon? This plugin looks much better than the one I'm currently using.
Or, even better, is it compatible with CB 1.4.6-R0.3?
I'll look into adding this functionality when I get home
Awesome plugin, definately going to use this. One suggestion however. Is there any possibility of adding different ban lenghs for players with certain permissions?