The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
![]()
I have not been at vB.org long, but sometime I would guess when vb3 hacks are accepted here is that many people will code hacks from previously made hacks which is not their ideas, and they will release other peoples ideas. Won't this arise as a conflict between authors and other members?
I think this will end up a big problem, alot of stealing of hack ideas and taking credit for it, basically all the new hackers will of released all the old skool hackers hacks. I think this is 90% probable, what do you guys think? Yes this will be a problem or no? |
#2
|
||||
|
||||
![]()
It WILL be a problem, and we have discussed this.
The polite thing to do is to ask permission from the original hack authors if you want to publically release a hack ported from vB2 to vB3. If you are doing it for your private site, no one can stop you of course. The only issue is releasing it publically and claiming credit for it. |
#3
|
||||
|
||||
![]()
I think an option in the release should be added:
"The author allows a VB3 release of this hack", same like the support one. A link to the original hack should be included automaticaly. What do you think guys? |
#4
|
||||
|
||||
![]()
hmmm, ive thought about this for a while to... I say do what teck says... however in some cases its not possible to ask for permission because many members have left such as bira, the polite thing to do would be give credit on the new thread... something like this
Original Idea came from: Name Orignal Hack Thread: www just a thought... my biggest worry would be to have the noobs code the better hacks over and have the noobs do a crappy job on them... I'd rather the better hacker do the hack. |
#5
|
||||
|
||||
![]()
Whenever someone is porting over a hack which wasn't his own idea, contact us.
As long as the author didn't give em permission and has not left from here at all, we will remove the hack immediatelly |
#6
|
||||
|
||||
![]() Quote:
![]() |
#7
|
||||
|
||||
![]()
I plan to convert mine to vb3 as quickli as possible ... in speculation, will there be much code change during the beta to stable version? Like do you suggest that I can code my hacks on a test board ready for when VB3 goes stable?
|
#8
|
||||
|
||||
![]()
From beta to stable? Should be minimal code changes, since it would be minor bug fixes, if any.
|
#9
|
||||
|
||||
![]()
Is there something in common from V2 to V3?
I mean the code or is that all new? |
#10
|
||||
|
||||
![]()
The only thing common to my knowledge is that it is abbreviated to vB
![]() I doubt any of the existing hacks for vB2 will work with vB3 ![]() For future reference : I will be upgrading ALL my hacks to vB3 once vB3 has become Final (and some during Beta I assume), so anyone copying my ideas of hacks are immediately requested to have the thread deleted ![]() ![]() BTW: I claim ownership of assassingod and NTLDR, so their hacks are mine too ![]() ![]() ![]() Satan |
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|