The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
#1
|
||||
|
||||
Just an observation
Often, somebody posts a new hack and several people jump right on the hack thread saying how wonderful it is - BEFORE they even install the hack.
Then, sometimes the bugs start showing up and we have a first page of "Wow, this hack is great!" and subsequent pages of "This sucks. It doesn't work." Later, people go to the hack thread and see the first page of "Awesome!" and try to install it and end up with nothing but problems. Then, they post, without reading the thread for possible fixes, about their problems. This bumps up the thread and somebody else sees the hack at the top of the heap, sees the "Awesome, wonderful!" comments on the first page, and the whole cycle repeats for a while. So, my comment is this. It might be best to WAIT and comment on the hack AFTER you have installed it. The concept of the hack may be cool, but if it doesn't work, your "Awesome" comment has just caused problems for some newbie. It is also better to WAIT and install the hack AFTER you have read the support thread, or at least skimmed it, all the way through. The same thing happens when Jelsoft releases an update. Somebody pounces on the announcement conversation thread with "Great! Congrats! I got the first post! Yay me!" and then later we see, "Uh, the upgrade isn't working." Why comment just to see yourself post? Save the comments for when you know that the released code works. Amy |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|