EasyBan
EasyBan
With this plugin you can ban griefers and other annoying people from your "offline" Server. To combat dynamic IPs EasyBan keeps track of players IP addresses and saves them into a file or database. Additionally you can ban entire subnets and/or countries if necessary. You can also add different DNSBL to block unwanted client hosts(open proxies, tor exit nodes, and much more). The plugin has support for Permissions (via bukkit API). When no Permissions plugin is installed all commands default to OP.
Features:
- Kick and ban players and all their IP addresses
- Temporary bans
- Ban entire subnets
- Ban entire countries
- Ban hosts with the help of DNSBL
- Customize plugin messages
- IPv6 support
- YAML, HSQLDB and MySQL database support
- Anonymous statistic reporting to mcstats.org.
- PHP Banlist
Installation | Configuration | Commands | Country Database | Changelog | Github | Support | Donate!
@wkera
well the fact that the plugin stoped being supported at 1.4.7
When player join him ip didn't add in the base, just adding NULL. I'm use 1.7.9 Anyone have idea?
@AS1LV3RN1NJA
Please see my preceding comment.
You should probably use a different bans plugin.
Is this plugin broken now?
Seems to just be adding '' as the IP when players join, meaning everyone gets banned and has to be whitelisted, effectively breaking the plugin.
I know the plugin is now inactive, but is there any chance of a fix for this issue?
Edit: Perhaps it's a problem with GeoIPTools.
EasyBan is Inactive and probably will not receive further updates.
@SpeedyBoy235
Send pull requests to the github repo: https://github.com/Fishrock123/EasyBan
I'll see if I can update it and re-release it; of course, with the authors' permission.
Please don't abandon this plugin :( we all love this plugin
I would like to help you out, but I don't think my java knowledge is sufficient (I've never developed plugins before, though I'm willing to learn), but if there's any other way I might be able to help you, please do send me a PM.
The issue is, it's more or less broken. Heck, I don;t even know if the newest version actually bans people by the following comments.
I no longer run a server, and never actually used the plugin myself, which causes huge issues. :/
That's a sad thing to hear, it's been a loyal and trustworthy companion in my battle against griefers for such a long time.
@zedadiaswick
@pimsserver
I have no idea. I am considering marking EasyBan as Inactive or Abandones as I no longer have the time to fix all it's weird nitpicks.
This can't be the only plugin with these features anymore.
EasyBan 3.0.5 Libigot: 214 (1.5.2-R0.2)
Issue: When banning a player, all goes well. The problem, however, is that there are no IPs stored in the database, which causes players to be able to reconnect them, even though their (exact same) username is already on the list.
Banning players does not save the ban to the DB:
I got around this by just converting that column into a basic text column. But now, although I am banned I can still connect. Banning me whilst online just outputs my ban reason in the chat. I suppose this could be caused by my modification to the database.
Any chance to fix this error?
@rekrutik
Does that work for pre-existing databases?
Hello, I had some problems with adding reasons of bans in Russian. So, will you add UTF8 support for the plugin? A custom version of EasyBan on my server already has that feature. If you want to add that, just replace in https://github.com/Fishrock123/EasyBan/blob/master/src/uk/org/whoami/easyban/datasource/MySQLDataSource.java#L55:
for:
And add a string in function setup():
That works fine.
Best regards, Rek.
@Fishrock123
Plus, if that were the case, your console would be logging an exception.
https://github.com/Fishrock123/EasyBan/blob/master/src/uk/org/whoami/easyban/EasyBan.java#L116
@dddeeefff
Nope.
getGeoIPLookup returns the geoIPLookup from GeoIPTools if it exists, else null.
https://github.com/Fishrock123/EasyBan/blob/master/src/uk/org/whoami/easyban/EasyBan.java#L199
Whichever that is set's the listener's geo variable to the GeoIPLookup or null.
https://github.com/Fishrock123/EasyBan/blob/master/src/uk/org/whoami/easyban/listener/EasyBanPlayerListener.java#L52
Annnd finally... EasyBan doesn't care if GeoIPTools is null.
https://github.com/Fishrock123/EasyBan/blob/master/src/uk/org/whoami/easyban/listener/EasyBanPlayerListener.java#L113
However it would be better if in getGeoIPLookup I did an instanceof check to make sure it is a geoIPLookup, that doesn't really matter here.
After some searching, I may have gotten the reason why. I think that if this line of code generates an exception, the listener won't be initialised: Line 133 in EasyBan.java:
I don't know, but if we don't have the geoIP plugin installed, will setGeo() generate the exception? The hunch is largely down to that the change between this and the last version, where setGeo() is not used here.
@ dddeeefff yes, that ist the corect Problem. The people they were banned can already join in v3.0.5.
When I go back to v3.0.4 the ban works perfect, banned players couldnĀ“t join.