[paul41598]

Yeah I could I guess...but then their posts wont be scored anymore. In other words, users can score their posts and if its a crap rating, and they get 6 for example in a given month, once they reach that 6, the cron job does it's dirty work right? If I take that 6 and bring it back down to 0, then noone will ever know what posts were scored low in the first place. Guess it doesnt matter, but just working for a workaround

----------------------------------------------------------
In fact heres a question that applies to what I could do. Firstly though, I have a text box where you can enter a number. "Score Amount" for example. If I put in a 6 there, then any users that have greater than 6, get the cron job run on em.

Ok now... what if in place of that, I made that text box so you could type in more than one number. Lets say (6,15,21) seperate by comma's. Then the cron job would somehow look through each of these numbers, compare it to the SQL where statement...and if a user has more than 6, execute the cron on them, then it keeps cycling through and if it finds that same user now has 15 bad scores, then it executes the cron, etc.