The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
People 'porting' Other People's 3.0.x Mods to 3.5.x
Does this behaviour bother anyone else?
Just because a modification works on 3.5 as well as 3.0, there's no reason to 'release' it in the 3.5 Forums if you didn't actually make it. |
#2
|
|||
|
|||
Well as always you're not supposed to re-release someone's code without their permission. If you think this is begin done feel free to report the post so a staff member can look into it.
|
#3
|
||||
|
||||
eg: https://vborg.vbsupport.ru/showthrea...threadid=93366
Not only is it doing exactly what my post is pointing out, but it is in the 'Latest Hacks' box...when it is really an incredibly old mod that happens to work on 3.5.x. |
#4
|
||||
|
||||
Well people should always tell the author of the original hack whether it be 3.0.X or 2.0.X or 3.5..doesnt matter..just always ask before porting..and if you ask and author says it is ok I think that it should be released in latest hacks, ect..for alot of hacks it isnt exactly EASY to port a hack from 3.0.X ask anyone..so why not give the person who took the time to port it over due credit??
~Curt |
#5
|
||||
|
||||
That's not the point at all.
In this case, no effort was expended on the part of the 'porter', just a simple copy/paste. Sure, they gave credit, but that shouldn't matter. Anyone with half a brain knows that the template structure of 3.5.x isn't very different to that of 3.0.x, and therefore most template mods will work on it out of the box. Hell, 80% of the custiomisation in my Steel styles comes directly from the 3.0.x Quick Tips and Customisations forum at vb.com. |
#6
|
||||
|
||||
People come here and ask how to lock a thread kall..do you really think that ALL 95,435 and growing members will understand the difference between 3.0.X and 3.5 template scructures?
~Curt |
#7
|
||||
|
||||
Quote:
I think that unless someone clearly specifies that they are willing to let other folks port their hacks then it should be left to the coder. If the coder has not logged in for a long time, then that doesn't give anyone license to use their code. However, I think that if you like the idea of the hack, it is okay to try to find a new and better way to do it, but make it clear that your hack was inspired by a different author/hack, etc.. That way it allows the author to update their hack as well. For instance - if someone came up with another shoutbox hack I think it would be OK to release it, as long as it doesn't use any of ZT's code, since it is not a new concept, but as long as the execution of it was new. |
#8
|
||||
|
||||
There is a THIN line between pircacy and imagination 0_o.
~Curt |
#9
|
|||
|
|||
Quote:
We don't want people posting these things because the doubles will just have to be merged when we move to the new hack database format. Plus most are probbly begin posted without the author's permission anyway. |
#10
|
||||
|
||||
That raises a good question, in the new hack database, how will it allow contributions? For example, lets say that there is a vb2 hack that only need 5 or 10 line changes to get it work on vb3 - could something like be 'contributed' to the hack in a way that others using vb3 could easilly find it?
edit to also add: Oh and will members be able to update versions a hack is compatable with after testing it themselves? |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|