The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
About to release a hack...
....me and my partners are about to release an online offline hack and we were wondering how it is you go about this.
Granted we need to make a thread in the released hack forum but what else should be know and be aware of. BTW the online offline hack can be seen: http://forums.otllive.com/showthread.php?threadid=498 |
#2
|
||||
|
||||
You should be aware of the following things when releasing a hack:
1.) That the hack does not already exist - If it does, be aware that people may try and ask you for support from the other hack(s) that exist, or you may get questions about something your hack does not do that the other one does/did... 2.) If the hack does exist, and is made for a vBulletin version newer than 2.2.0, be prepared for people to make comparisons between scripts, and sometimes for people to question whether it was your idea and whether the coding is 100% yours... 3.) If the hack is an addon or modifications of a new or old version of a hack, be prepared to ask permission from the Original hack author before releasing... 4.) Be prepared to state whether you are offering Support or not...If you are, tick the box in the thread, and state in the Post where you are offering support to the hack...The common assumption is that you are only offering support in the thread, but some people may ask you questions via PM or Email... State if you do or do not wish for people to ask for support via Instant Messenger(s) [aim,msn,yahoo,icq etc], PM and Email... 5.) Be prepared to be asked for either a Live Demo or Screenshots of the hack, and some people will ask more complicated questions, such as things like "How many queries will this modification add to my *name*.php file?" or similar... Thats about all you should be aware of as regards to members... 6.) Another thing, which is not necessary, but makes sure than non-liscenced members cannot get the hack, is to attach it in a file...Even a single line modification of code should be put in a .txt attachment, or if it contains replacement variables such as {.imagesfolder.} (remove the "."s), attach it in a .php file as the vBulletin will not parse it... That should help answer your question Satan |
#3
|
||||
|
||||
Haha this looks quite cool :P
|
#4
|
||||
|
||||
It's good...
Just one notice - What if the user doesn't use an Avatar Satan |
#5
|
|||
|
|||
Thanks for the replies, I will take all this into account.
Our hack should be posted in the full release section soon. |
#6
|
||||
|
||||
Ok cool
I look forward to looking at the code Satan |
#7
|
|||
|
|||
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|