IP-Check
A typical IPC Report for a player with multiple accounts...
My staff wanted a way to check for players who were using multiple accounts easily, especially those who like to bypass bans. So, my solution to their dilemma was this plugin.
With IP-Check, you can log every account a user ever makes, across every IP, and keep track of them all. It supports cross-IP logging, as well as account limiting and filtering. Don't like it when people have more than one account? Stop them! IP-Check comes with Secure Mode, in which you can define a number of accounts that players can have. Players may then have up to that many number of accounts, and any other accounts will not be permitted to join, even across different IPs! Or, for an added effect, it can even ban the account.
IP-Check can also notify you whenever a multi-accounter logs into your server. Simply set the number of accounts players may have, and any time a player logs on with more than that number of accounts, you'll receive a warning about it. If they are in violation of your rules, you can ban them! But banning each account one at a time is long and time-consuming. With IP-Check, we've summed that all up into one simple command. When issued, IP-Check will take the players IP, ban all the accounts linked to it, and then ban the IP itself. Or if you've accidentally banned the wrong account, there's a command to unban them all as well.
IP-Check supports logging with MySQL and SQLite. It has no external dependencies, and installation is as simple as dragging and dropping the plugin file and restarting your server.
Login Notifications with Simple Notifications enabled
Reporting Plugin Issues and Bugs:
All issues are now handled through GitHub. If you would like to report an issue, please visit the GitHub Issue Tracker.
Support is currently only offered for IP-Check v2.x (build 2053+). It is recommended that you update to the latest build and enable Automatic Updates so that you may receive bug fixes and patches as they are released. No support is offered for any build of IP-Check v1.x. Support is NOT offered for IP-Check v3.0.0 or v3.0.1.
NOTICE: If you are receiving messages in IPC Reports about GeoIP Services not being available, you need to download the GeoIP Database from MaxMind.com and copy it to the data folder for IP-Check. It can be downloaded from this link: GeoIP (Note, you need extract the .gz file using WinRAR or 7-Zip.)
Metrics Usage Disclaimer:
This plugin utilizes Metrics in it's code. Metrics is a system which records anonymous data about the usage of the plugin and reports it to mcstats.org where it is displayed publicly. This information cannot be used to identify your server in any way. The information collected includes but is not limited to; the version of IP-Check you are using, what version of Java you have, what operating system you are running, whether your server is online or offline, and the number of players on your server. If you would like to see the information Metrics has collected, you can view it here: Metrics Profile
Questions or Comments? Post them below! All feed-back is appreciated.
Care to donate?
A lot of work and time has gone into developing this plugin. If you'd like to donate, click button below .
All donations are greatly appreciated and help in future development of IP-Check. We help to help others.
@xBlueXFoxx
I'd recommend updating to 2.0.2 first and seeing if the problem continues to occur. If so, let me know and I'll look into it.
-Jnk
Every time I enter an /ipc command it returns "[IP-Check] An invalid command was specified."
3:34:12 PM CONSOLE: ERROR]: [IP-Check] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '-check.ipcheck_user' at line 1 3:34:12 PM CONSOLE: ERROR]: Error occurred while enabling IP-Check v2.0.1 (Is it up to date?)
5:00:07 PM CONSOLE: ERROR]: Could not pass event PlayerLoginEvent to IP-Check v2.0.1
@xPaulienx
The actual "auto-ban" feature of IP-Check is Active Mode. This should be set to false in the configuration to disable this function.
If, however, you're referring to people simply not being able to join under an IP after you've /ipc ban'd someone, that's simply because the IP-Address is banned with Bukkit.
You can avoid this for the time being by simply performing ./ipc sban on the player you wish to ban. This is identical to the default ban command offered by Bukkit.
As we have a server for as well legal as 'illegal' players, a lot of people have more accounts. Which we don't mind, but they all got banned! Is there some way to turn the auto-ban off? We used to have the plugin but because of the automatic banning we don't use it anymore. If there would be a way to fix it, I would definitely want to hear that!
@xBlueXFoxx
Not at the moment, no.
There are multiple reasons for this, honestly. The most prominent of which is the fact that I've not had the time necessary to convert the plugin over to UUID usage, but also because I just finished rewriting the plugin not but two or three months ago, and to incorporate such a change would have drastic effects on the plugin's current systems.
In laymens terms, IP-Check would realistically have to be split off into two separate development branches, one for 1.7.9+, and one for 1.7.8 and lower. This would be a developmental burden.
More logically, the way IP-Check is designed to operate, encorporating UUIDs would only constitute a minor addition to security. UUIDs, frankly, provide little to no extra security to IP-Check than usernames do. This is simply because, when a person makes a different account on Minecraft, IP-Check will still detect that user because of their IP. The same goes if they change their name through Mojang's API. The only difference here is that, with UUIDs, the name change could still be detected even if it occurred with an IP change occurred as well, whereas the current name-based system could not. This advantage by itself, however, does not constitute the necessary reasons for the above to occur.
Does this also log player UUID's?
@Jnk1296
Thanks for the quick response :) I guess for now we'll just set the ban message through IPC as well :)
@buzzsaw100
If you look on Essentials, you'll see the players you ban still have the message you set.
IP-Check does not in any way, shape, or form use information from Essentials. It does not access it's ban messages. All that happens is that when you perform a check on a banned player, the plugin sees this player is banned and updates it's database to reflect this. Because it does not access Essentials, it set's it's own logged ban message to whatever you have saved to IP-Check's configuration.
It's something to be addressed in due time, but I don't have the time for it at the moment. Sorry.
Love the plugin, only problem is it overrides ban messages that we set with essentials even when we have this. Or is it some other setting?
should-manage-bans: false
@xPaulienx
Yes, players have to log in for IP-Check to register them. IP-Check does not run off of player data stored in Essentials or in your world file. It has it's own database that it references.
Also if you'd like to not be spammed by multiple account messages, you can exempt the player that's causing the messages to appear via ./ipc exempt <player>. Or if you'd like to turn the messages off completely you can set notify-on-login to false in your configuration.
I'm glad to hear you like the plugin. :)
Really like this one. It's nice to have an overview to see if someone has multiple accounts. That's the number one reason we put this in our server. I've used this now for a couple hours and I like it and it comes in handy, but I do have a few negative points about this plugin. - After the server has restarted with the new plugin, I wanted to do an ipc on someone. I got the message that user or IP was not found. So I found out that people have to login first, after the server restart, to do an ipc check on them. I'm not sure if that's something that happens with all the plugins, it was just something that I found quite inconvenient. (Maybe the /reload command would help?) -Another thing is that I got the message <name> has multiple accounts! very often. It almost got spammed in the chat and I thought to myself that one message would be enough. But in the end, I really like it and it's a great plugin.
@Jnk1296
Allright thanks! My mods can help now =D
@Dyllaann
Whoops. Totally forgot that perm when I remade the page.
Permission is ipcheck.getnotify.
What is the permission for the join message. Tried a lot, but my moderators still cant see.
@Jnk1296
Yay! :) (i hope). Lets test this baby :3
Version 2.0.2 build 2057 has been uploaded. This build addresses several bugs and issues with the plugin, including some issues which have been addressed in the comments.
@Wolfen2448
Hi Wolfen2448. I used "should-ban-on-secure-kick: false" and "should-manage-bans: false" in the config of IP-Check. Also, the ban message must be something like "ban-message: The Ban Hammer Has Spoken" (you must write the same message that your Essentials use for banned users, shown when a player is banned and he tryes to enter your server). In this way, both Essentials and IP-Check messages will be the same (for banned players). I'm using the configs in this way with success. I hope this helps you. Just my 2 cents. Regards. :)
@Fighter88
Doesn't work :l
@Wolfen2448
Carry an anti permissions ( - -ipcheck.ban) 2x - - ;)