Go to my site, scroll down and look at vBTrends if you're so inclined. I put it on my site, and they went up, so I threw it out there for anyone who might care to use it.
Maybe vbTrends is responsible. I should called it vbTrends - Improve Registration Rates.
I'm teasing you, don't get mad at me
On a serious note:
It's a dangerous road to go down when we start having staff evaluate mods. I'm not saying there isn't something that can be, or needs to be done, but, we have to approach this carefully.
It's not just a matter of being subject to staff opinions on new mods - it's also a practical matter of time. We'll end up with a 'new mod' queue and you'll wait weeks or months for your mod to get approved. I've dealt with this at SMF and do NOT want to see it here.
Quote:
Originally Posted by EnIgMa1234
yes but people should search to see if the hack already exists. their has to be over 20 adsence ones, basically telling you to do the same thing
This is, as I've stated before, a fault in the search.
Yes, some people will not search before they post a new mod. Yes, some people will post a mod even if it is a duplicate. But many people simply fail to find other mods with the limits of search. Search was built for threads, not a mod database. We have no tagging per say, no naming conventions, and even the 'thread prefixes' that we do have are confusing enough that I basically don't bother with them.
At a minimum, I recommend implementing a warning on similar threads at the time the user attempts to post the new mod thread. This isn't hard - it's basically a variation on my vbPostCheck hack. "The following similar mods where found - you might want to review them before completing your submission." or some such.
If fact, on a similar tangent - I recommend the same thing for questions in the support forums. "The following similar threads where found - you might want to review them before submitting your support question."
04-30-2007, 06:02 PM
Threaded Mode