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!
Comments
-
_ForgeUser7585445 Owner
-
_ForgeUser7462391 Author
-
Forge_User_65370702 Contributor
-
View User Profile
-
Send Message
Posted Apr 19, 2013@Kaosvf
@phades99
It should be able to work without SQL.
@dddeeefff
I honestly have no idea. Feel free to dig around in the source: https://github.com/Fishrock123/EasyBan
-
View User Profile
-
Send Message
Posted Apr 7, 2013Got this error in the latest version using /ewhitelist:
Also, banning doesn't appear to work. Downgrading now, I think.
Yup, downgraded and a ban worked. The test bans I made on the most recent version were recorded, however; it must only fail to stop people joining
-
View User Profile
-
Send Message
Posted Apr 7, 2013@phades99
I have the same problem.
-
View User Profile
-
Send Message
Posted Apr 5, 2013When i do /eban phades99 it kicks me but i do not get banned... Does this plugin need a sql?
-
View User Profile
-
Send Message
Posted Mar 31, 2013@dddeeefff
No idea. It might be a spigot thing. EasyBan ignores the GeoIP stuff if GeoIPTools doesn't exist...
-
View User Profile
-
Send Message
Posted Mar 31, 2013@Fishrock123
@daisyduck1
I'm getting this in console on startup:
Could this be connected? I'm not going to try out this version on a public server because of it. It did this on build #735 of spigot (built on #2717 of craftbukkit) which is a version for 1.5.1
-
View User Profile
-
Send Message
Posted Mar 30, 2013@MDRunaway
Fine, I'll make aliases. Stupid essentials.
It will probably take me a while to get around to it.
-
View User Profile
-
Send Message
Posted Mar 30, 2013@Fishrock123
You Miss Understood me :D I mean the /eban cmd is identical with the one from essentials ;) Can you change that? :) Because otherwise essantials + easyban ban the player and he get now ban reason after a reconnect and is permanantly banned...
-
View User Profile
-
Send Message
Posted Mar 25, 2013@ Fishrock123: I check bans.yml and the whitelist ist totaly empty. I never used the whitelist bevor.
-
View User Profile
-
Send Message
Posted Mar 25, 2013@daisyduck1
Can you check for me if the people who could join in 3.0.5 were whitelisted?
-
View User Profile
-
Send Message
Posted Mar 25, 2013Thank you Fishrock for the fast answer, but i think you missunterstand my question. Sorry for my english, because I am from Germany.
I want to say. All people they where banned in v3.0.4, they can now join in v3.0.5.
When I changed back to v3.0.4 than they still be banned again and can´t join.
-
View User Profile
-
Send Message
Posted Mar 24, 2013@daisyduck1
Name bans > whitelist > IP bans.
Whitelisted people are now ignored by IP bans.
-
View User Profile
-
Send Message
Posted Mar 24, 2013At first, thank you for the update ;-).
I used v3.0.4 with a MySql-Database before.
Yesterday i installed the new v3.0.5. I get no error, everything is fine, the config is still the same with the data of my MySyl-Database. But people they where banned before in the Version v3.0.4 can now join the Server.
Is there anyone with the same problem?
Now i go back to v3.0.4 and everything is ok. Maybe there is a bug in v3.0.5?
-
View User Profile
-
Send Message
Posted Mar 20, 2013Thanks for the update.
Edit: Also, 17k downloads, nice!
-
View User Profile
-
Send Message
Posted Mar 17, 2013@limon4eg
Thanks for your mundane input?
-
View User Profile
-
Send Message
Posted Mar 17, 2013Upgrade to 1.4.7
-
View User Profile
-
Send Message
Posted Mar 9, 2013@MDRunaway
The command is already not /ban. it is /eban. refer to /help easyban
-
View User Profile
-
Send Message
Posted Mar 9, 2013In the next update whitelisted players will have priority over IP bans.
They can still be name-banned, though.
-
View User Profile
-
Send Message
Posted Mar 1, 2013Got another idea: We have problems with people getting their IP when their sibling is banned. Whilst this is a very helpful feature in terms of keeping people with hundreds of alt accounts from launching grief attacks on the server, there are specific users for whom we have to keep manually clearing ip bans in order to let them back on the server.
This happens because when a banned account connects to the server, it logs the IP before disconnecting them for being banned. As a result, every time the banned sibling tries to connect, the not-banned sibling can't connect any more, and they have to contact us and wait for us to manually disable it.
At any rate, can you design a solution for this? I came up with some possible ideas:
-
View User Profile
-
Send Message
Posted Feb 22, 2013Can you make another ban command like /easyban username reason time because the ban cmd is identical with the one from essantials. I Hope you do this ;)