Multiple account login detector (AE Detector)

If you are like me and migrated from .threads, a common modification was an "AE detector", a simple mod that saved a cookie of a history of ids logged into on your site. If someone logged into more than one account, you got a PM letting you know that your site was being accessed from multiple accounts.

Over the years this was very helpful in identifying users who were posting under multiple accounts (alter-egos!) and users who would return after being banned.

You might be wondering why I don't use the vbcookie call - well, thats because on logout all vB cookies are cleared, so we need to store a cookie that is not effected by the login/logout process.

New Installation
1. Add New Product with attached XML
2. Go to vBulletin Options -> AE Multiple Login Detection Settings and set your specific settings.

Time to install: Easy - 2 minutes.

Upgrade
If you installed this as a Plug-in manually, you can delete that plugin and install this Product, just make sure to go into the Options and set them accordingly.

I hope you find this useful and will click INSTALL if you use it; should it prove useful to enough people I can look at making this installation more automated without the need for edits and an Admin Options page.

To upgrade you will want to reimport this XML file and edit your options accordingly.

1.0.3
-----
. Added a check to ensure that users weren't deleted when reporting violations
. added htmlspecialchars_uni call to username

Note: I am unable to get the call to construct_phrase with $vbphrase['multiplelogin_alert'] to work reliably, as such the $message variable is still set manually inside the plug-in and not via the phrase. If anyone has an idea of why this might not always work, I'm all ears.

1.0.2
-----
. Updated to include exclusion groups, users
. Changed so PM is sent by ae sender id

1.0.1
-----
. Released as a Product (thank you PHPGeek2k3 for your help)
. Added option to post to a forum versus send a PM (or both)
. All settings moved into Admin Option

1.0.0
-----
Initial release.

[MPDev]

All that is stored in the cookies are userids; if your userids change, then you will have a problem with it tripping on all your users.

[cOuNtErFiET]

ok i had this on my board, my board went down had to redo the whole thing reinstalled this, and now everyone is tripping, but i redid the db also so what can i do to fix this need this working asap if you can help

thanks
CF

[bashy]

It will only go off if,

the persons are using the same computer,
The persons have not deleted thier cookies!,

Failing that thier not the same persons

[Absolution]

I've also tried this on 3.6 and it doesn't seem to be working. I logged on a completely different computer and created two accounts and successfully logged into both.

[attroll]

I installed this in my test site and longged in as two different users and nothing happened. It should have tripped and reported then to my PM, email and posted in the forum I specified and it does not do any of these.

I am running vB 3.6.1. Does this work with this version?

[attroll]

I think I have this working now.

[FlyBoy73]

Compatible with 3.6.1?

[brvheart]

3.6 version here

[angelo]

Originally Posted by cOuNtErFiET

ok i had this on my board, my board went down had to redo the whole thing reinstalled this, and now everyone is tripping, but i redid the db also so what can i do to fix this need this working asap if you can help

thanks
CF

I'm having the same problem, some of my USERID's changed and now im getting a constant stream of "tripped accounts" when i only had a few each day before my board was reinstalled.

Is there a way i can reinstall this plugin but maybe change the name of the cookie that AE Detector sends out that way it won't read the old cookies on people's computers?

[MPDev]

Originally Posted by angelo

I'm having the same problem, some of my USERID's changed and now im getting a constant stream of "tripped accounts" when i only had a few each day before my board was reinstalled.

Is there a way i can reinstall this plugin but maybe change the name of the cookie that AE Detector sends out that way it won't read the old cookies on people's computers?

If your userids changed; then my only suggestion would be to modify the name of the cookie in the plugin code itself.