The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
Multiple Account Detection & Prevention Details »» | |||||||||||||||||||||||||||||||||||||||
It happens all of the time. Some members will make multiple accounts to back their own opinion or get an extra vote in a poll. Here's a modification that will detect and prevent multiple accounts, as well as notify the administration about multiple accounts. Inspiration for this modification came from the work of MPDev (creator of the Multiple Account Login Detector) and randominity (creator of the Multiple Account Registration Prevention). This is basically a combination of those two modifications but with new and improved functionality.
This is not an update to the "Multiple Account Login Detector (AE Detector)" nor is it an update to the "Multiple Account Registration Prevention." If you have either one of these (or both of them) installed, you should uninstall them before installing this modification. With the initial release of Multiple Account Detection & Prevention, I believe that I have fixed previous bugs/complications as well as improved the efficiency and logic of the code. This is my first publicly released modification. I would appreciate any comments and suggestions! Confirmed! This works perfectly on all vBulletin 3.6, 3.7, and 3.8 versions. Unfortunately, I cannot give support right now. I may be able to help periodically, but until my schedule yields some more free time, I won't be much support. Please check back in a week or two. Basic Details File Edits: None Template Edits: None New Files: 6 Hooks/Plugins: 3 Global Phrases: 36 Install Time: 2 Minutes or Less Install Difficulty: None, Very Easy Features and Settings - Login Detection - Registration Prevention (Multiple Methods) - Ignore Child Accounts - Ignored Users - Ignored Usergroups - Ignored ISPs - Prevention Usergroup - IP Address Based Prevention - Extended IP Address Prevention - IP Address Time Inclusion - Banned Account Check - Primary Banned Usergroup - Cookie Expiration Time - Cookie Refreshing - Cookie Name - Cookie Reset - Multiple Account Reporter - Reports via PM - PM Report Recipients - Reports via New Thread - Forum for Report Threads - Verbose Mode - BB Codes: LIST, URL, CODE How it Works With every newly recognized login/registration, an account-counting cookie is set (or added onto) with the member's User ID. Depending on the settings, Multiple Account Detection & Prevention will analyze the cookie during login/registration to see if there are any multiple accounts. Login Detection offers cookie-checking and reporting. Registration Prevention offers the same thing, plus more advanced features. First of all, when it prevents an account from registering, it actually moves the registrant to the Prevention Usergroup so that the administration can review the case. This also allows for customized privileges for recognized multiple registrants. Registration Prevention also has IP address detection which finds out just as much information about users. Depending on an administrator's preference, this modification can also reban a new registrant if one of their previous accounts has been banned. In fact, if the administration wishes, multiple registrants can simply be denied registration all together. Whenever there is a detection/prevention, the modification will report the information to the administration through private messages, a new thread, or both (depending on settings). The Multiple Account Reporter can be any valid user. Known Issues - vB Optimise users: Reporting via thread seems to get messed up by vB Optimise, so try reporting via PM instead. - PhotoPost vBGallery users: The registration handling appears to not work properly when PhotoPost vBGallery is enabled. From what I can tell, these known clashes have been caused by the other modification's coding. The author of vB Optimise will not even work with me to fix it. Until they improve their coding, I'm not sure if I can do anything about these issues. As far as I know, administrators that do not use the above modifications will not have any problems. Installation / Upgrade Unzip the package (madp.zip), upload the files to your forum location, and import the product file (allow overwrite if upgrading). Please read the ReadMe.txt file that is packaged with the modification for more information. Please remember to mark this modification as installed if you use it! If you like it, nominate it for the Mod of the Month! Thank you! Download Now
Screenshots
Show Your Support
|
3 благодарности(ей) от: | ||
aeturner89, Filgga, ricardoNJ |
Comments |
#12
|
|||
|
|||
I'll definitely give this addon a try. Almost anything that sends a forum arzehole to hell is appreaciated.
Trust me, forum trolls and fake user are a plague. |
#13
|
|||
|
|||
hello. is it bug-free? or a beta?
|
#14
|
|||
|
|||
Quote:
Quote:
Quote:
Yes, it is bug-free. The latest version (1.0.1) is stable and there are no known issues, and it should work flawlessly. |
#15
|
|||
|
|||
a German translation, there is not it?
|
#16
|
|||
|
|||
The file in the root "Madp" copy? OKEY, you must also create htaccess?
|
#17
|
||||
|
||||
On my site, I have a few members who live in the same address. If they both take turns on their pc, this will detect them & ban them?
Is there a way to stop that from happening. If not, this could be a bad idea for some boards. |
#18
|
|||
|
|||
Kiros72, please help me.
|
#19
|
|||
|
|||
I'm sorry, but I do not know German. =[
Quote:
Quote:
If you do not want to receive the notifications for those users who use the same computer, then add one of their User ID numbers to the Ignored Users and enable Ignore Child Accounts. With Ignore Child Accounts enabled, as long as a user is seen as a multiple of an ignored user (or Usergroup), the user will be ignored from any kind of detection. Would that solve your problem? |
#20
|
|||
|
|||
Hello Kiros72.
1st I should therefore have the files directly into the root copy, but the whole folder named "madp"? ok what I understood. 2nd why no htaccess file? dan but everyone can access it or I see this wrong? I do not want a door for a hacker up. do you? |
#21
|
|||
|
|||
1: Your forum root folder is the root that I'm talking about. If your forums are located at www.example.com/forums/, then the forum root is the /forums/ directory. You must upload all of the contents (files and folders) of the 'upload' folder into your forum root.
2: All files in a default vBulletin installation are publicly accessible. There's no reason to make the files private as long as there is no room for an exploit. Since these files contain the plugin code and nothing more, it would not do anyone any good to try to access these files. Therefore, no .htaccess is needed. |
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|