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.
@Jnk1296 When they try to login with their 1st account it results banned for multiaccount.
As far as Lite Mode development goes (2.1.x development), the following appears to be what I will most likely go for as far as programming goes;
2.0.x - All Modes and functions controlled by the Player Login Listener (PLL)
2.1.x - All Modes and functions will be stored in FunctionModules controlled by a ModuleController or FunctionController (not sure which I'll call it yet. XP)
Current Potential Modules List:
-All Modules (with the exception of SYSTEM_CORE) may be disabled and will be non-dependent on each other for operation. Lite Mode will function primarily by selectively disabling these modules as necessary.
Feedback? :D
EDIT: Oh, and the above changes will most likely constitute a support break for the 2.0.x series. I have a feeling this system would cause a good bit of change to the current under-lying system structure.
@Kaiort
I can't find anything in the code that would cause this issue by itself. How are you determining that these players are being banned?
Man you plugins is awesome but I have a problem.
I have it set like this but when people create a second account they aren't kicked but istantly banned.
@Adzdon
Glad to hear it. :)
I'm liking this plugin
v2.0.6 is up and waiting on Bukkit approval. This release fixes bugs with Localization support!.Additionally, it makes changes to existing localization keys, so be sure to update your localization libraries to reflect these changes!
@Jnk1296
Alright, so, I found the problem... and apparently it's something that most likely affects all 2.x.x versions of IP-Check and possibly the 1.5.x series as well. An older version of the Localization Manager placed the prefix "translation." in front of all localization values called from a localization index, and, as a result, this was accidentally included in the 2.x rewrite and resulted in every localization key called from a localization index returning a null value, causing the plugin to fallback to it's default translation.
TL;DR: A certain intelligence-challenged developer (myself) accidentally broke the Localization Manager during the 2.x rewrite. :D Expect a fix shortly...
@ZwingGX
No idea what the issue is at the moment, though I do know that whatever the issue is, it's in the commons layer and not within IP-Check itself. Looking into it. :)
@Jnk1296
IP-Check v2.0.5 and IP-Check v2.0.3
Localization doesn't work :(
my config: https://dl.dropboxusercontent.com/u/78671707/ip/config.yml
my local file: https://dl.dropboxusercontent.com/u/78671707/ip/kr.yml
@ThisUsernameIsMine
Yeah, from what I understand, Bukkit isn't doing quite the same depth of code checking as they used to. But, hey, just means faster approval times. xP
@Jnk1296
approved after 15 minutes? not sure if that's a good or bad sign xd
Thanks buddy, it works again :-)
@ThisUsernameIsMine
lol yeah... the whole reason that happened is because I derped and swapped around a couple of loading instructions, so the load sequence was out of order. XD
Pulled 2.0.4 from download, 2.0.5 is up and waiting on Bukkit.
@Jnk1296
np. atleast it didn't format my hdd :P
Looking forward to the upcoming changelog :D
@ThisUsernameIsMine
...
You know what....
I think this problem stems from a sliiiiight case of tiredness/stupidity on my part.... I miiiiight have uploaded the wrong build. xD
whereas 2.0.3 worked fine, 2.0.4 doesn't seem to function, at all (the below problems even occur after deleting the old config):
- plugin loads but throws a NPE in console at startup/shutdown: http://dev.bukkit.org/paste/10830/
- none of the commands work anymore (it replies with "[IP-Check] An invalid command was specified", to any command i issue)
The above issues occur with both my existing config AND with a NEWLY generated (default) config, under Spigot 1.7.10-R0.1-SNAPSHOT #1649 + Spigot patch 20141001a @ Windows 7 Ultimate x64 running Java 8 Update 25 (x64)
@Jnk1296
Thanks for this :)
Otherwise this is a great plugin, very usefull :)
@Jnk1296
Cross that. The reason IP-Check doesn't monitor the banned status of IPs directly from Bukkit is because there IS NO API call available to do that. :PP The only way I can do that by the looks of it is to manually scan in the banned-ips.txt and read it line by line, which is terrible for performance...
Lite Version, though, I can do. That will likely constitute a v2.1.0 release.
@jorrik98
Take a look at the picture at the top of the page. The internal error occurs from trying to pull information from the GeoIP module when it's not initialized, throwing a null pointer. I have been able to reproduce this behavior as well.
The IP-Ban fails to register due in-part to the way IP-Check manages it's database, and in part due to how you are banning the player. By only IP-Banning the player and not banning the name as well, IP-Check will only check the player name, see that it is not banned with bukkit and update itself, and Bukkit, accordingly. This is an oversight on the program. I'll address this with the update as well.
As far as your request for a non-banning version, I'll see about setting up a Lite Mode.
-Jnk
@Jnk1296
I'm using a custom banning system, which might cause it, as disabling GeoIP handler doesn not change anything. This might explain why the internal error occurs on the line where 'player banned: (state)' should be. Currently I have to disable IP-Check to be able to IP-ban someone, as when I Ip ban someone with IP-Check enabled, the ban does not register in the banned-ips file. Is it possible to release a version which does not affect the bans at all, and just checs for alts, IP's, and GeoIP?
Thanks