Technically, the IP address checks would come through if they used the same proxy server to register multiple accounts. Also, if the cookie information is passed through the proxy (which it should be for them to be able to login to vBulletin), then the cookie detection will also work.

Correct. In version 1.x no action is taken for login detections. Action is only taken for registration prevention (if you enable it to).

The difference is plenty. MPDev's modification only detects logins. My modification detects logins and registrations and can prevent registrations as well. During registration, advanced IP checks can also take place if the administrator configures the options that way. Speaking of options, there are far more settings and features. There is also much better documentation for all of the configurations. My modification also uses faster functions (like explode() instead of split()) and in my opinion, it also has better logic within the code. On top of everything else, I provide support for my modification. I don't see too much support coming from MPDev, himself. I don't think that his/her modification is bad, but I honestly think that mine is better. That's the whole reason I built this modification up; I saw that major improvements could be made upon the idea.

Feel free to take my modification for a test-drive. You can always uninstall it and go back to the AE Detector if you want (everything will still work as it did before).

Also, you should not have my modification installed while the AE Detector is installed. Just chose one or the other.

Multiple Account Detection & Prevention is NOT supposed to ban for multiple logins. It is only supposed to ban multiple registrants if you have it configured to do so. This was a multiple login detection, not a registration detection. In other words, the person just logged into another account; he/she did not make a new one.

Get it? :)

Thanks.
i'll try your mod..it seems promising.
so do i have to uninstall AE detector mod first?
and i fear if your mod will move users or prevent from registrations to non-spammers too? as if someone surf on cybercafe and multiple users register there but they arent same but then ur mod will prevent them from registering?

i mean to ask wht does ur mod use to detect and prevent multiple registration?
wll it prevent non-spammers too anyway?

Is there any plan to fix the glitch regarding vBOptimize being installed?

You should uninstall AE detector completely (not just disable) for it to function properly. (You can see by the comments that this has been verified again and again)

You can CHOOSE whether or not multiple accounts are moved to a prevention usergroup. Also, if you do choose to have multiple accounts moved to a prevention usergroup, you can always choose to move them to a new usergroup, after you verify they aren't a spammer/multiple account. (This does NOT stop them from registering.)

It's pretty much impossible to tell the difference between Spammer and non-Spammer by simply checking IP addresses or cookies. If you're worried about real, unique users being moved to a prevention usergroup, you can always activate "silent mode" which will ONLY notify you. (It will not take any actions in silent mode) This will help you get an idea of how many reports you can be expecting and give you an idea of how it works.

how do I uninstall.. I did a test and now can't get into my admin...

Warning: require_once([path]/madp/detection.php) [function.require-once]: failed to open stream: No such file or directory in [path]/includes/functions_login.php(185) : eval()'d code on line 3

I want those instantly banned too.
Can you add this too ?
What about my suggestion? Can a few $ put it in front of the cue ?

I couldn't have said it better myself. Okay, well I would have added a few more things, but I'll do that now ;)

This modification will always check for a cookie that tracks which account the person has logged into. This happens for both registration and login. You can enable IP address detection for registration; this is to protect against someone clearing or modifying their cookies to get past the detection. Since IP addresses change and some (although very few) people may register while at a public place (i.e. library or cafe), I also include a time limit. This setting limits the time (in days) in which the modification will look for matching IP addresses. Take this scenario for example:

You have the IP address checks enabled and you have the time limit set to 30 days. Someone registers on a public computer. Two months later, another person registers on the same computer. Although they might have matching IP addresses, the modification knows to ignore it since it is past the time limit of 30 days.

So I would like to confirm this for you. You have nothing to worry about. You will be able to reverse anything (such as bans or changed usergroups) and you can uninstall it at any time and reinstall AE Detector with no permanent consequences. :)

Unfortunately, the author of vBOptimise refuses to respond to my private messages. I cannot find anything wrong with my code, so I think he/she will have to be the one to fix this glitch. If I need to change something, then I will gladly, but again, I cannot find anything wrong with my code. Please notify the author of vBOptimise about this inconvenience. He/she might know what to do.

It looks like you don't have the files correctly uploaded. The files within the 'upload' folder should be uploaded to your forum root. Once you have the files in place, it will work just fine. I can help you with this privately if you would like my assistance.

If you just want to uninstall it, you will need to add this line near the top of your config.php file:

Reupload your config.php file and all hooks will be disabled. You will be able to login and modify whatever you need to.

Yes, I'll have actions available for multiple logins for my next major release.
Also, yes, money always helps. I work on projects that I get paid for before I work on projects that I wouldn't get paid for.

It would be good to have more functions to deal with returning banned members / trolls that keep opening new accounts.

Here's a functionality request / suggestion:

Have a usergoup that is not able to log out. Members in that usergroup are automatically forwarded to a site of your choice.

This way, returning trolls could silently be moved to this usergoup. They would not be able to log out except by clearing cookies.

Logician once created a code that disallowed banned members from logging out.

Hmm, while I do make other modifications (privately), this one modification has a set theme: detecting and preventing multiple accounts. Your suggestion is for a modification that deals with banned users, which is not what this modification is about. If you would like me to create a modification for such a purpose, I'll get around to it when I have the time. It's a good idea, though ;)

Yes, thats true. Such modification would be a wonderful addition to the functionality that the MAD&P is offering.

Please create this modification when you find the time.