AntiMulti
This is AntiMulti. It is a plugin designed to prevent the use of alternate accounts from the same IP address. To put it simply, a player cannot use multiple accounts on the same IP address and likewise, will not be able to use a ton of IPs.
Download: Download
AntiMulti is a plugin which has undergone multiple changes from its original intent to be a simple plugin to prevent alternate accounts from being used on a server by blocking too many accounts from sharing an IP to a plugin which can also prevent session stealing using this same concept and also supporting admin protection. This is done simply by using an IP system to prevent the unauthorized use of an account by using IPs to prevent session stealing from working in the first place. All of this is completely toggle-able in the configuration file in case one does not use want to use certain features or not.
There are a few things you must understand when using this plugin. This is not a one-hit wonder in that it can stop all alternate accounts, as proxies would be able to get around this system, however common proxies would eventually be blocked after they are used enough. This does its best though to stop a member from simply using 2 accounts to gain an advantage over another player.
There are 2 groups this plugin will understand: Players and Admins. Players are normal players and are not forced to use the protection system as strictly as admins. Players are more loosely held initially by allowing more connections per name and IP, however this can be changed. Admins are more protected to prevent the taking of the account to cause problems by forcing registration and using a smaller range of names and IPs that can those accounts can share. This is all permission based in that there is a perm that designates whether the player is an admin or a player, which is just antimulti.admin, which if given, marks the player as an admin and handles them accordingly.
We do have Metrics with this plugin, so stats will be sent to our mcstats page if you are opt-ed in, where that config is located in the PluginMetrics folder.
If you have any issues, please create a ticket here with the log file and as much information as you can provide so the issue can be investigated and handled. If you have a question, feel free to ask here but please read everything first before you ask since your question may have already been answered elsewhere.
Okay:
@mcheaven
Yeah, might be good to know what problems xAuth has to I dont have to deal with people complaining about it.
@Icelord871 thats great I like second jars :D (I dont like Essentials...) if you make an xAuth clone, remember to fix the async thread issues.. should I make a list of things that should be done with xAuth? :D
@mcheaven
I will see what can be done. I might have a second jar that uses xAuth's db and reads it all thru that. I prefer actually having separate jars so that I can get multiple things working at the same time and thus, have better updates. First release might just be a xAuth clone running with this.
@Icelord871 yes please do this :) you are my hero x) but please use the same db format like xauth or a way to update to yours because I used xauth for months.. (many passwords and accounts..)
Cause a few people asked about xAuth and this, and since xAuth has the source in github, I might be able to merge both of them together. Although I may split this into multiple jars, since there is so much being added and I know that people dont want everything (*cough* Essentials *cough*) I may start splitting the project into a few jars where each has a specific function (and can run independently)
I thought about this to request an implemting into xAuth :/ but now I think about an implementing of xAuth into this :D
1.6 uploaded, waiting for verification. Has a new perm and the config is fully added
I think what I might do is use some sort of algorithm to decrease the file size. That way it can store more and means that I can speed it up a bit when checking. But idk yet. Trying to fix a few problems I have encountered when adding a config and mySQL at the same time, so I am seeing where I screwed up.
@Icelord871
I think EasyBan has an efficient way to trace one player by nick/IP. It uses IDs and each player has an ID.
@Lord_Ralex
Awesome
@Brustus
At the moment, it is possible, but i will be doing a major remake of all of the data. It was more of a way for me to make it work, and now that I have an idea of what people want, I will be changing alot of it.
Looking forward to this when the IP sharing becomes more functional. Keep up the good work!
Fixing 1.5, it will (hopefully) use the config to allow you to change the kicking messages that they when either the whitelist is active or their IP is already registered
Right now, I do plan on seriously redoing its use of IP sharing, but I definitely get what you are saying here. I am trying to see what the best way to do this while making it run as fast as possible, so I am focusing on speed a bit more, because if it really slows the server down, it will not be used alot. If I have to cut out features to keep it running fast and smoothly, then I may create addons and have them be optional.
As for the register, I was going to have it set so that they can create a password at any time, but in order for them to be able to log in with a different IP, they will have to enter that password to be able to do anything.
Right now, you can use /am add [name] and the player can log in even if the IP they use is registered to another player. However, it is a global effect, which I will be changing.
I have alot of plans for this, this is just the beginning.
I don't have much time so I need your answer:
screenshot
http://s017.radikal.ru/i416/1112/a8/b178a8c85d8e.jpg
The only feature what I need is to list player's names and IPs (Currently using EasyBan but it's outdated.)
1st command is /ealternative <name>
2nd /ehistory <name>
But there's also a command to see who (nicks) joined the game with an IP.
But it's not all. The problem is that our xAuth prevents users to register more than 1 account per IP.
So it will be perfect if the plugin would add his name/IP to the database after entering a command like /register or /login (should be configurable).
Hope you understood me. If not then ask =)
Yea there's a lot of work for you, good luck!
Hey, keep up your work it's what I need!
Version 1.4.10 is out, it will generate the folder on its own now, so the installation page will be updated once the jar is uploaded and ready to be distributed
I have just gotten a friend of mine to help with coding this. He is currently working on using a better search engine to help speed the plugin up. So, 1.4 and 1.5 are currently under development
Currently working on 1.4.x, which will include a configuration file, wont have much to configure in it, but you will be able to change the message players see when they are not allowed to log in.