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.
No wait, that code in that rar file I have already, the dates for it precede what I have printed out. I should be fine. Just asking those questions because from what I see in the code, that is what it does
Oh come on, after i printed out the code for the one he had out on Jan 5, there is a newer one?! Great.
@Lord_Ralex
I dont really know :/ please take a look on the source _Robert made an updatet version source: http://dl.dropbox.com/u/40068360/xAuth-Source.rar
Plans for 1.8: Improve the error reporter, it just records errors, not the locations, fix the config setup, change the saving and loading, prepare the config for mySQL and flat file usages, and get my own login system integrated.
As for xAuth, does it take your inventories away when you logout and has you get it back when you login? And same with your location? Because if it does, then that means alot of work for me.
And testers would be nice XD. Once i get a working 1.8 beta I can shoot it to those that want to test it for me and give me reports on it
mhm :< i can be tester! send me PM at forum :D
okay good idea :) please make it as fast as you can I'll tell many xAuth users about your plugin when its done
Yeah, what I probably will do is have my own login and registration system and use that, but if the server has xAuth or AuthMe installed to not use my system to avoid conflict. And once I get my system done, then I have to make a jar that will convert from the 2 plugins to what mine will use. Which means a ton of work.
And also create a new file system that reduces internal memory use but might mean a slower login. And make it more protected with hacked clients. The joy of it all.
nice :) now you can start with the xAuth part :D
Updated (finally). Error reporting is working fine, added a new bypass using /am add [name] [ip] for a better bypass system, and fixed bugs.
I hate myself once again, I just noticed the perms for the commands don't work either. The antimulti.whitelist one works fine because of the way it is used, but the commands are not. They don't work unless you are oped. So, means I will have to fix that later. So, 1.7 means the perms will be changed to reflect that. 1.8 should fix that. Also working with xAuth and seeing the best way to get that dealt with. I expect 2.0 to have that done.
@Lord_Ralex
I can't wait :)
Okay, 1.7 will be out this weekend, with it are bug fixes, which that one bug is driving me crazy, the error logger, and the new bypass system. I will also start adding in the registration section to get a registration jar ready, since xAuth has a book for it codes. And the way it saves means a lot of work to get it to convert to mine easily.
Apparently there is a bug that we found while just explaining this to a server owner. We noticed that the plugin would let a player login, then logout, then a second account would try to use that IP would be kicked, and it would cause both of then to not connect. Not sure exactly the cause, but I will fix this in 1.7, which is getting done.
1.7 will have an improved bypass system, the ability to enable or disable the IP share blocking feature, an error-reporter, and hopefully a registration system (might make this a separate jar instead so I can release 1.7 faster)
@Lord_Ralex
wow sorry about that :O
My computer is kinda angry at me...
Apparently... the code I had with 1.6 is gone... so I have to edit a 1.3.24 and get it caught up.
Well, 1.7 is actually atm just a complete redo of the entire plugin. I decided to rewrite nearly most of the code and start integrating my own registration, which is going to be my remake of XAuth. As with the mySQL, still trying to get the bloody thing to work.
So really, 1.7 will be a complete overhaul and include a much-improved allowance of multiple accounts, a new search (i think it might be slower, but is more efficient), and the error-reporter, which will log all java errors to a file that includes your AM version, bukkit version, and the pex version if you have it.
@Lord_Ralex
good :) this will help mutch in the future.. because many will have your plugin and if they have errors most of them would just say "I HAVE AN ERROR!!" ..
Working on 1.7, with a new error reporter that will try to store errors in a file that can be sent much easier and will include information to help me.
@Icelord871 okay thank you :) I will advertise for your plugin when you implemented xauth and fixed it (important are 1 and 5 so please fix them first :)
@mcheaven
3) Yes, it will be, cause I will most likely end up with a xAuth copy that uses the data from the original and uses it with mine
5) I will see the direct cause of it
1) Right now, multi-threading is not implemented, and when i first release the copy, i might remove the multi-threading, then find a better way to use it.
2) I have to see what is going on here
4) might use my own commands for everything, so it is not just a xAuth copy, so it might end up with /am import h2 (so one could go from on to the other, not sure about it though)
Thanks for all the links, and it will take a bit to get all of this done. I might have the merge finished in 2.0, which may take a bit to get to, since repairing and modifications may take a bit. I plan on 1.7 having the mySQL completely fixed and running, so I can then focus on the merger.