The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
General coding practice for vB mods
I know I'm going to be a pain in the arse asking this, because I'm sure I've seen soething about it somewhere already, but is there a thread anywhere with a general practice for releasing a vB modification?
I don't mean the tutorials or the api but some kind of 'standard' for MOd auhtors to follow for the installation notes, etc, etc.? |
#2
|
|||
|
|||
Installation notes should be clear, a .txt file is what most use, some build an html page so it looks nice.
If your modification edits the .php files you should use a find/replace method instead of telling people to search for line numbers. The reason for this is once you install a hack the line numbers will change, and future vBulletin versions may break the line numbers as well. You should zip all the required files up, this just makes it easier to keep track of everything once it's downloaded. |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|