WhoBannedMe
WhoBannedMe
Description
The offical FishBans API plugin to let you know how many global bans a user has. When a player connects, other users can be notified if the connecting user has any global bans from the various ban systems Fishbans pulls data from. This plugin is developed in-house by Fishbans, so you can be assured it will always be up-to-date!
These services include:
- McBans
- McBouncer
- Minebans
- McBlockIt Legacy Data
- Glizer
Permissions and Commands
| Command | Permission Node | Description |
| N/A | whobannedme.exempt | Allows user to bypass ban lookup on connect |
| N/A | whobannedme.notify | Users will be notified when a connecting player has more than the minimum-bans count |
| N/A | whobannedme.notify.all | Users will be notified of all connecting players |
| /whobanned <username> | whobannedme.lookup | Lookup number of bans on a player |
| /whobanned details <username> | whobannedme.lookup.details | Lookup detailed ban information on a player |
Configuration
See detailed configuration on Github.
Development Builds
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.
You can find development builds on the WhoBannedMe Development Artifact Server. These builds are not guaranteed to perform correctly, but offer the latest features we are working on.
The config.yml may need to be updated to take advantage of these new features. You can find the development version of the config.yml on Github.
Source
Find our source on Github!
Notes
Data collection
WhoBannedMe uses Plugin Metrics that collects anonymous statistic data about the plugins usage and sends it to http://mcstats.org/plugin/WhoBannedMe
Update Checker
WhoBannedMe now includes an automated update check. This option can be disabled in the config.yml.
Planned Additions
- Configurable option to list detailed ban information in game
- Auto kick/ban of players with more bans than limit set in config
Known Bugs
- Original v1.1 requires debug-mode to be enabled for proper reporting on player login. All downloads of v1.1 after 0100 EDT on 31-Mar-14 do not have this bug
Comments
-
_ForgeUser6848545 Owner
-
View User Profile
-
Send Message
Posted Dec 22, 2015@verservarlin
The crazy thing is, I would be happy to maintain this for them. Yet... "in house" seems to be the choice.
-
View User Profile
-
Send Message
Posted Dec 20, 2015"so you can be assured it will always be up-to-date!" taps foot
-
View User Profile
-
Send Message
Posted Mar 24, 2015Is there a 1.8 version planned?
-
View User Profile
-
Send Message
Posted Apr 3, 2014@pookshuman
It means that Fishbans no longer actively collects new ban information from those services. MCBlockIt is currently non-operational. See This post for why McBans data is no longer being collected.
Fishbans maintains the ban data for those services from when it was actively collecting data from them, but no longer gets new ban data from them.
-
View User Profile
-
Send Message
Posted Apr 3, 2014could you explain what "legacy data" means?
-
View User Profile
-
Send Message
Posted Apr 2, 2014@Shahblox
It pulls ban data from the global ban services listed at the top of this page. It will not include any ban data from Essentials or similar plugins that only handle local server bans.
-
View User Profile
-
Send Message
Posted Apr 2, 2014Can it see if players are banned through another plugin besides essentials?