The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
||||
|
||||
![]() Quote:
|
#12
|
||||
|
||||
![]() Quote:
|
#13
|
||||
|
||||
![]() Quote:
Everyone wants something different I guess. I enjoy what people can do with things I make. There are many valuable ideas that spawn from feedback of people that put the code into operation. I do not see a value myself on making a product for someone to turn around and insult them for their lack of talent. Every person has skills in their own fields I do not see a problem. This site is for owners of vBulletin to customize their site. I was on this site for 2 years before I did much of anything. |
#14
|
|||
|
|||
![]()
I personally like to give feedback where credit is due and always click the install button. Its the little things that go a long way.
|
#15
|
||||
|
||||
![]()
Clicking on Install and a thank you is all I would like, it gives me a feeling of a job well done.
That and if there are support questions for my modifications, the person gives as much detail to the problem as possible, more info = quicker and more accurate support. |
#16
|
||||
|
||||
![]() Quote:
|
#17
|
||||
|
||||
![]() Quote:
|
#18
|
|||
|
|||
![]() Quote:
Quote:
![]() I only contributed one extension so far which proofed to be very useful for me so I thought "why not share it". I'm trying to support it. I am generally a bit offended by the addons/ext/hacks here who start their post with a two site long essay on how to click install, vote for HotM, credit, thank, donate, whatever. This should be a free place where the content is the focus not the people who contribute. I got a lot of ideas for hacks here and generally modifiy things before they actually go on my installation and I'm glad if it's just a product.xml or a code bit which I can use how I want. I think the most important things you can do is: 1. Install it on your installation and report if it works (especially useful if you use a lot of other addons/ext/hacks). 2. If it fails report back with a full list of installed addons/ext/hacks, vB version, OS, and so on, so I can try to find out what's wrong. 3. Give suggestions what to improve and/or ask what it is about and what exactly it does. It's often when you write something for your own it might be a mystery for you what it actually does. I'm also a bit suprises by the lack of documentation here, I'd expect at last a basic explanation how your addon/ext/hack works! I can check the source code but I guess you can not, so you're basically at the coder's mercy, he can do with you want he wants. So don't hesitate to ask questions if you're not sure about something! Went a bit off-topic here but it's what I wanted to say for a long time ![]() |
#19
|
||||
|
||||
![]()
The one thing I like to see non-coders do is to answer help questions that they can. If somebody asks how to do something basic with a mod, and you know the answer, jump in and help out
![]() Answer questions in General Vbulletin Questions too. People need help with basic, built-in vbulletin functionality from time to time. |
#20
|
||||
|
||||
![]() Quote:
|
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|