The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
An observation.
So, I have been a proud VB owner for about 2 months now and previous to that I was a keen YaBBer. I am new here so am still getting to grips with whats going on in and around the place but I have made one observation that is quite annoying me. Feel free to shoot me down, but I feel I must point this out to you and offer what I would consider as a reasonable solution.
I'm only talking about the VB3 section of the hacks section as that is the only area I have been looking around and installing hacks from, although I'm sure its the same in VB2. When a hack is released there follows a mass of postings of errors/problems/arguments/rubbish.. resulting in large pages of duplicated things which is a nightmare to go through, causing even more postings of errors/problems/arguments/rubbish due to the fact that some people are to lazy to go through the previous 40+ pages of errors/problems/arguments/rubbish. Not only do the hack installers have to go through all this, but the Hack creator is expected to go through all this and weed out the useful bug reports/compliments.... it's not clean and it is certainly not efficient. I realise a moderator in no way could control all this that is happening at once, so, onto my proposed solution. We trust a hacker to write and release a hack that we will then install.. So hows about we trust the said hacker to moderate his/her own thread..Thus bringing some control back into the thread and cleaning and tidying duplicate errors/questions so every page then becomes useful. We're all admins here after all so we should know what we are doing. Now obviously this can be elaborated on as I haven't thought it entirely through but I hope you understand where I'm coming from. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|