The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
||||
|
||||
Quote:
|
#12
|
|||
|
|||
You can read the requirements in the License Agreement
Quote:
|
#13
|
|||
|
|||
Quote:
There is a rating bar and the comment section available to every addon. These two ensure that users can share their experience regarding addons. I at least browse through the comments section and take a closer look at the last entries and also on the response rate of coders who marked "supported" = yes before I consider even downloading a addon. We all have time limitations but addons whose coders never updated in month while there are nasty bugs reported are a no-go for me. Security and stability rule, rest drools. Testdriving on a non-productive server is not always an option because what seems to work or at lest doesn't harm can later show its real implications. I trust in the opinion of other coders which "control" the source of other coder's addons. |
#14
|
||||
|
||||
Maybe you should actually do your research and not just install any random mod because it looks good. Rather than expecting everyone else to police the mods for your convenience. You do realise nobody here is paid for the work they release, right?
|
#15
|
|||
|
|||
Quote:
Also seeing as this is a members board - maybe asking the members once in a while what they want may help instead of always telling us what we cant have. |
#16
|
|||
|
|||
Quote:
sometimes, people are asking too much... sometimes... |
#17
|
||||
|
||||
Quote:
FYI - I do read the entire mod thread, and I DO indeed do my own research, so you may can the attidude. So what's your point? Are you saying that since something is available at no charge, it's ok to have serious flaws, and that people should just accept those serious flaws, and just shut up about them?? Anyone that actually believes that, should not post their work in the first place. |
#18
|
||||
|
||||
Quote:
|
#19
|
||||
|
||||
|
#20
|
||||
|
||||
Sometimes too many rules will cause users to not take that first step and post their first modification. They get too worried they are going to break a rule and get their mod pulled. So, it's better to gently lead them down the right path. If they did something 'wrong' in their modification, you send them a nice PM or make a post with suggestions on what to add next - "Sometimes new people unfamiliar with modifications will install a new mod and then decide they don't need it and go to uninstall it and don't understand how to do so correctly, especially when there are files uploaded. It's a really good idea to include uninstall instructions that detail exactly what to do for these newbies." Most coders what to do it right and being polite while pointing out a problem will be much more effective than adding a rule.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|