The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#181
|
||||
|
||||
Quote:
It's a hack that I really would like to have but I'll be the first to admit, I AM NOT a coder...that's why I come HERE. Like Paul mentioned earlier in the thread, he's codes but doesn't design, I design but don't code. Liz |
#182
|
||||
|
||||
Quote:
|
#183
|
||||
|
||||
Quote:
|
#184
|
||||
|
||||
Quote:
However, my point remains - These are Free Hacks. I have no real complaint if no one answers because I have no $ investment. |
#185
|
||||
|
||||
Quote:
|
#186
|
||||
|
||||
Quote:
|
#187
|
||||
|
||||
There seem to be two discussions here. Allow me to explain...
If I release a mod to the public (2 so far :classic: ) I'll support it the best that I can. I feel that I have an obligation to those who use it. It is not only my mod but my reputation on the line. The threads in the question forums I'll sift through and answer the ones I think will work. I've only been a part of the vB community for two months and it would be quite irresponsible of me if I send someone on a wrong path just because I wanted to help but had nothing to back it up. Mistakes will happen of course but that's life. So if I reply to to a thread I'll go back with intent until the problem has been resolved or if I run out of suggestions. There are many who'll search and try to find the answers on their own before asking their question(s). There are those who are not as resourceful and will ask immediately. My guess is that many contributers are turned off by the latter group. I strongly believe in the "pay it forward" concept in that if you've received help then you help others. As huge as this community is with all of the personalities I think overall the people here practice that concept. They seem to enjoy what they do and are happy to help. Their time is on a voluntary basis and that says a lot. I think there's a good thing going on here and I'm glad to be a part of it. |
#188
|
||||
|
||||
Quote:
|
#189
|
|||
|
|||
I've probably mentioned this before but I think part of the reason some newbies find it hard to find the required answers is how long some threads become and especially because the same thread will cover different versions of the same hack - so an earlier bug may have been fixed in a later version but you have to read through all of the thread to work that out. (I've done this myself - read through a long thread, missed one particular post that addressed the problem I had and have to be pointed back to the original answer - that's not laziness it's just in an 18 page thread you do tend to miss things!)
I suggested it before but perhaps allow the hack poster to mark posts as "answered" or somehow otherwise collapse all the responses to previous versions. Or perhaps have it so that each new version of a hack starts a new "sub thread"? That way people only need to read through the content that is relevant to the current release? |
#190
|
||||
|
||||
Quote:
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|