Well, I didn't really consider that at first. I originally set out to upset that. But the more you and others typed, the more I realized most want transparency. So, no big deal. I'm getting mellower with age. ;)

It's done and working. I need a break and I'll take a look with fresh eyes in a while, run a test and post code. I want to be available when I post in case I missed something.

If you think about it, transparency is better for something like this as the bots won't see anything different and won't know what is up on the surface. If they experience changes in the way things usually are, they can adapt that much quicker. Simplicity at it's finest, so to speak.

Posted for your review.

:D installed thanks.

Will this work with 3.6.8?

I'm planning on upgrading but won't have time to reinstall all my mods for at least three weeks.

Not working for me.

I add the product but then when I hit Register, accept the terms and click continue it says I left a required field blank (never shows the form to register).

I am using this alongside the ajax registration and am using recaptcha as my image verification

It might. I'm running it on www.riderinfo.com on vBulletin 3.6.10

Did you do the template edits in the instructions? Without them, that is exactly what will happen. Check your ACP settings for Stop the Registration Bots too.

I had the same problem. Went back and triple-checked that I had added the correct hidden fields to the correct templates as described in the text file. I had done everything correctly.

However, I had used some really long hidden field names using a mixture of upper-case letters, lower-case letters, and numbers. On a hunch I changed the hidden field names to some 8-to-10 character all lower-case letters and it started working.

Thanks for the heads up. I didn't make any notes on the limitations of those fill ins.

I'm thinking of automating the process 100% and generating everything random on a per registration basis and using the table we have to store the values.

I edited the description fields to add text that clears that up. It should help.

We also eliminated 4 of the fill in fields and made them auto generated. We track them via the db and that makes things very random. The only field that won't change names unless the admin updates it is the hash field name on the rules and user reg page. Changing them once in a while will keep things very confusing.

I'm trying to get as close to possible to set it and forget it. We may me able to make a cron job that resets those too so things shake up very often and random.