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.
@Lord_Ralex
Ok because m server is getting hack, what old version before this update im think of using the older version for now till you found ou the problem
@chopstick121
I have been staring at it for days, amidst medical issues. The issue is making no sense as the screenshot is contradicting what should be happening, and another dev looked at it and is not certain what is causing it. I am trying to find the reason for it but it is taking some time.
When will this be fix!
@Lord_Ralex
still the same thing
I believe the bug is patched in the 2.0.5 Build 2: https://github.com/LordRalex/AntiMulti/downloads Once it is confirmed to not exist, I will release it here.
@Lord_Ralex
no
@chopstick121
:/ Seems like a bug in my checks. Does it still let you log in though?
@Lord_Ralex
i turn off online=false but after that i got it fix and now it said you have no reason to login This the config:Your text to link here...
@chopstick121
Can you open a ticket with the config and the server properties? and what version and build?
Why does it keep saying you are not register?
@codydbgt
Can you open a ticket and post the config then? Want to know what is triggering it to not want to....
saying you must have a reason to log in :|
umm its not login players in :| even when we we register.
@joannou1
Okay, the patch for the event is out, so I will work on getting this patched for 1.3.1. https://github.com/downloads/LordRalex/AntiMulti/AntiMulti%202.0.5%20Build%201.jar is the patched version. the mysql setting is in place, but is not tested completely.
@joannou1
While I have watched the devs talk, I use an event with appears to cause lag with 1.3.1, more specifically the Chat Event, and from what I understand, the event is causing major issues for servers and is advised to be avoided. Since it is only 1 event for now, I am holding off on updating, since creating an entire new version to patch a small bug is not worth it, especially with the progress I am making with implementing a mySQL database with the plugin, which is coming along quite nicely. What I will possibly do is create a dev build with the chat event removed so that it would not cause further issues, but it would have the mySQL setup also, which is not fully tested either. I will look into it.
@Lord_Ralex
Oh come on. My friend Tim (Frostbrood) is working with Bukkit for today to help them out. They have a few perfectly operational dev builds working. He said they are nearly complete.
I will not recommend using this on 1.3.1 for bug related issues. I will not work with supporting until bukkit has either a beta or a RB
Patched a bug in 2.0.4, also ignore the sql part, that is in 2.1.0
This is really a great plugin. Juts yesterday my server got DDoSed by some guy using over 50 different accounts. Now, this will hopefully prevent it!
Version 2.0.4 is released: - Removed Vault dependency - Patched login bug - Few internal changes
I have patched a few things from the 2.0.3 version, however, I will not release that version until Bukkit releases a dev build/RB for 1.3 just so that I can make sure everything works correctly. However, you can download the 2.0.4 version from the github download page.