If you want to use the IP Address Prevention, then you can also make use of the Ignored ISPs field. By default, "aol.com" is already there. Basically, anyone's IP address that resolves to being from AOL will be ignored from the IP address checks.

You can add or remove ISPs in the Ignored ISPs section if you want, but I strongly recommend keeping "aol.com" in there.

Hey, everyone. I need to make a small announcement.

Due to some personal issues, I cannot work on this modification as much as I intended - at least for the next week or two. I was planning to have version 2.0.0 finished up within the next 3 or 4 days, but I'm going to have to postpone this.

Sorry about the inconvenience. Version 1.1.1 will still be supported.

I'm wondering if this will still work with the old cookies from the mods that inspired this? I've been using the AE detector + MAD but I'm having a few issues and have looked through this code and I don't detect any problems with the IDstack cookie not being compatible. Thought I'd ask though.

Also, small bug, although it won't matter anyway:

... has a typo. It's set to 'false' so I guess it doesn't matter much. :)

Yes, this will work perfectly fine with the old cookie. Just make sure to keep the Cookie Name set to "IDstack" (without quotes).

Heh, I wouldn't really call that a bug since it doesn't affect anything. But thank you for finding that typo! I'll fix it up in the next version. :)

Sweet hack...! :up: :up: :up:

Hi,

I installed this mod yesterday, thank you!

The threads that are being generated that inform me of a detection aren't displaying any information.

Attachment 93314

This is my settings.

Registration Prevention - Move to Specific Usergroup
Silent Mode - No
Ignore Child Accounts - Yes
Prevention Usergroup - 4
IP Address Prevention - Yes
Extended IP Address Prevention - Yes
IP Address Time Inclusion - 60
Banned Account Check - Yes

Attachment 93315

I was using the AE Detector before and worked ok but I want something that will check new members against previously banned members.

Any help would be appreciated!

Thanks! :)

That's strange. I've encountered this before while I was in the beta stages of coding version 1.1.0. I can't exactly remember the exact cause of it, but I know that this can also happen because of phrasing errors.

Do you still have the AE Detector installed?
Do you have a good bit of modifications installed?
What version of vBulletin are you using?
Do you know if this only happens for logins or for registration preventions?

You might want to try fiddling with the reporting options. For instance, disable verbose mode and enable private message reporting (also set your username for the recipient).

i have had this installed since it was released and was working fine until today and now i having same issues as glennybee The threads that are being generated that inform me of a detection aren't displaying any information

Hmm... I'm sorry to hear that.

I know that version 1.1.0 is working fine on my vBulletin 3.8.0 RC 2 installation.

I'll look into version 1.1.1 a little later today. In the meantime, try to uninstall/reinstall or at least try it with verbose mode disabled.

I'm using v3.8. I suppose I do have a lot of mods but it's not extensive.

I did have AE Detector but I uninstalled it before installing this mod.

I disabled prevention and I am still getting blank reports and members are being moved to the moderated usergroup.