MineBans
MineBans - The Fair Global Banning System
Put simply, MineBans is a global banning system for Minecraft servers. We offer a way for server admins to publish the player bans they make on their servers to our database. The owners of other servers can then use this information to decide if a player that just joined their server should be allowed to stay.
How Does it Work ?
When a player joins the server a summary of any previous bans they may have is downloaded from minebans.com and the following checks are done on the user
- Is the player on the local exception list, if they are let them join.
- Is the player banned from this server (global, local or temporary), if they are prevent the connection.
- Is the player banned from another server with the same owner, if they are prevent the connection.
- Is the player using a public proxy, if they are prevent the connection.
- Is the player using a Minecraft account that is known to be compromised, if they are prevent the connection.
- Does the player have too many bans from other servers, if they have prevent the connection. Each of these checks is fully configurable.
What About MCBans, MCBlockIt, Glizer, etc
The way I see it MineBans is nothing like the other systems available for a few reasons (feel free to judge for yourself though):
- Our ban reasons are fixed. This means that the plugin can collect supporting evidence for each ban. Ultimately this means instead of a single word, "xray" as the ban reason we can provide a full page of statistics and calculations. As the bans are backed up by data we believe they are much more trustworthy. (At the time of writing over 80% of our bans have supporting evidence)
- We don't track players, we only collect the necessary information from the server. There is no log of who logged in to a specific server or how long they were online.
- Less potential for abuse. Did you know the MCBans team could globally ban a player from all servers for no good reason, with MineBans there is no concepts of a system wide ban like this. Did you also know that the MCBans team can configure their plugin (without your consent) to broadcast a message of their choice when a player joins, this has previously been used for political messages unrelated to Minecraft. There is no such feature with MineBans. The compromised account feature is the only way that a player could be banned incorrectly and you are free to disable that feature if you do not trust the origin of the data.
Some Things you Should Know
- All moderators of the server will need an account at minebans.com. This might seem like an unnecessary pain but it allows us to hold a certain player responsible if the system is abused without having to take a drastic step like removing all of the servers bans from the database. It also will help to prevent abuse of the system as a valid Minecraft account is needed to sign up.
Installation
This is a summary of the information that can be found on the wiki
- Sign up for an account on our website
- Download the plugin from the files page and put the .jar in your plugins folder
- Run the server once for the config file to be created and then shut it down again
- Open the config.yml file and edit the api-key option so that it matches the value from the My Servers page on the website
- Give your admins and moderators the necessary permissions
Usage
The basic commands are listed here, for more information please see the commands page on the wiki. All commands can be used with no arguments to show usage information.
- /ban - Bans a player from the server. Requires the minebans.admin.ban permission.
- /unban - Removes any bans that a player currently has. Requires the minebans.admin.ban permission.
- /kick - Disconnects a player from the server. Requires the minebans.admin.kick.
- /exempt - Used to manage the exempt list. The exempt lists acts as a list of players that will be made exempt from the join checks meaning they can join even if they are over the servers limits. Requires the minebans.admin.exempt permission.
- /minebans - Provides various commands relating to the system.
Since the page needs some colour here is an example of an in-game lookup
The colours next to each reason denote that ban's severity. Limits can be configured for each ban reason and each severity.
For Developers
The plugin provides it's own API for other plugins to use, the features provided by this are documented in detail on the GitHub wiki page.
Contributing
Contributions to the project are very much welcome, if you have a feature that you want implemented and know a nice way to do it then consider forking the repo and submitting a pull request. These will be accepted as long as the following simple guidelines are followed.
- Do not edit the structure of the pom.xml file, feel free to add a dependency if you need it but the formatting and structure should not be changed.
- If you are exposing a new API method, add a JavaDoc comment to it, but don't over-comment internal code.
- Follow the existing code style, don't antagonise over every space though !
All dependencies that are used are now available from a public Maven repo, so you don't have to worry about building several other projects just to add a simple change any more.
Source Code
Dev Builds
Changes Since Last Release
Download
Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.
http://bukkit.jacekk.co.uk:8000/job/MineBans/
@wide_load
Derjyn :)
@minedworp
I knew it worked :P No problem anyway.
@wide_load
All done and set up thanks for the quick reply and help
Great work
@minedworp
Done :D
You need to upload the skin to your character, you do that by logging in to minecraft.net. Once it's uploaded click the verify button. Once your account is verified you can change it back to what ever you like.
@wide_load
My mincraft name is mindworp but i entered Mindworp on the register form
could you pls reset it to mindworp pls
also im new to this so could you explain how/what im suppose to do with the skin?
Many Thanks
@Derjyn
:P Sorry about that, could you tell me your player name so I can look into the skin thing. It's probably the cache on my server not obeying my headers.
I will keep on the good work :D I'm glad to hear you like the project ;)
Just updated to the new plugin, only to get a message that v0.10.2 was out :P
As for the skin issue at the website... it's not a cache issue. I have my browsers setup so that cache, history, cookies, etc are cleared automatically on browser close. Problem is there in both Firefox and Chrome, so it doesn't seem to be a quirk of a specific browser.
Keep up the good work. I like this plugin, and it will most certainly be on my "must-have" list, especially once all the wrinkles get ironed out.
@minedworp
The skin is still done by username, here's mine for example http://s3.amazonaws.com/MinecraftSkins/wide_load.png so you should be okay. The names are case-sensitive though so if you are getting an error it might be that. Let me know and I can update your name if you typed it all lower case :)
Migrated accounts from mojang i dont think are supported by control panel on minebans.com?
i login to minecraft.net with my email and not my username as my account is migrated
Does the verify account option validate usernames only ?
Because it says my minecraft account is not valid when it checks it for my username .
Should it also check emails for usernames also?
@Derjyn
NoCheatPlus is effectively the same as NoCheat but with a few of the exploits fixed, personally I prefer the idea of a fresh start with AntiCheat. you can just ignore the warning, I will be adding support soon enough.
Interesting about your skin, could you try a CTRL + F5 to see if it's a browser caching issue, if that fixes it it's a very simple fix :P
Good to see those bugs being squashed. I'll give NoCheatPlus a test and see if it's a worthy alternative to AntiCheat.
A note about the skin though- I registered my account nearly a week ago, and that verification skin is still there.
@Bintin00
Actually never mind I figured out what's wrong, fix in progress :D
@Bintin00
Are you using a VPS ? Either way could you email me at [email protected] with a bit of information on your host so I can test :)
@Derjyn
RE: Update notifications The log you posted shows MineBans v0.10. There was a problem with the version number 0.10 being read as 0.1 from the plugin.yml file you can see that being fixed here https://github.com/betterphp/MineBans/commit/712d9d7ce9d5c830d57244005fbca9f6de9e9428 Weirdly the version on the files page has "0.10" in it's plugin.yml file, when I tested the update checker the RSS feed had probably not updated which meant that this was hidden. I re-uploaded 0.10.1 with the correct version number here http://dev.bukkit.org/server-mods/minebans/files/5-v0-10-1/ Also worth mentioning that you can remove the permission if you don;t want to get update notifications :)
RE: AntiCheat There is also NoCheatPlus which is a fork/continuation of the old NoCheat. AntiCheat is not supported yet due to limitations of the data it provides to other plugins, you can ignore the warning.
RE: Skin The skin images are cached on my server to speed up load time and be nicer to Mojang, it should update within 6 hours.
Hi, i'm getting this error
23:28:21 CONSOLE: [SEVERE] [MineBans v0.10]: Failed to create system ID: null 23:28:21 MineBans: Disabling MineBans v0.10 23:28:21 MineBans: v0.10]: Disabled. 23:28:22 CONSOLE: [SEVERE] Error occurred while enabling MineBans v0.10 (Is it up to date?)
Hello, first some facts:
Using MineBans v0.10.1
Using AntiCheat v1.3.3
MineBans complains:
In game, MineBans informs/annoys me about there being an updated version, and that I should download v0.10.1.
NoCheat is abandoned, and AntiCheat appears to be it's successor. I am running the latest version of MineBans. Also, on the website, my avatar has not changed from the verification skin. When bugs like this (easy to fix and hard to miss), get through, I worry about the more intricate innards of a program, plugin, whatever...
@wide_load I sent you a email with my config.
@wide_load
I tried it again. It doesn't work.
@ProG28
Well it looks like the config isn't updated, so could you try stopping the server then editing the file and restarting it after ?
If you want you could email the file to [email protected] and I can take a look to make sure it's okay ? Don't post it publicly though since the API key could be used to issue bans from your server if someone has the same IP.
I restarted my server after I changed the API-key