VB3 hacks ?

[grog6]

Hi, I'd like to ask a question concerning future VB3 hacks ...

Do you think, authors of Vb 2.x.x hacks should adapt them to work on a 3.0 version ? Is it the best thing to do ?

What do you think of it ?! :paranoid:

[Erwin]

That's up to the authors of the hack, isn't it? :)

[Xenon]

i will add all my hacks to vb3 when i find the time.

but because of the large codechanges i'll just port over the ideas, but code em up from the bottom.

but some of the hacks will become useless as they are already in vb3 ;)

[grog6]

Hehe, ok, will do the same thing if there is no feature already included in VB3 :)

Is VB3's code really different from vb2.xx ? :-/

[Brad]

Yes the code is different, and thats a good thing!.

[filburt1]

FWIW I've stumbled upon some vB3 prototype forums here (i.e., hack forums for vB3) so we're already planning for such things here. :)

[RDX1]

Is it going to be like over at wbbmods, when wbb2 was released?

[amykhar]

What concerns me is that some of the beta testers might be "converting" the work of existing hacks and then releasing them as their own work because they have the jump on timing, having had the code for so long.

Amy

[filburt1]

It's a bad idea at all to use a beta version as a reference, let alone to edit it.

[assassingod]

I dont think beta users were/are allowed to edit the code in the first place?:confused:

[amykhar]

Not on the live boards, but I'd be willing to bet anything they have been investigating the code on their test boards.

Amy

[Chris M]

Probably;)

But that means that they will be able to re-release their own hacks in vB3 format, or create new ones;)

Satan

[kdog316]

do you have any links to these hacked vb3 boards filburt

[Chris Gwynne]

No vB3 boards are currently allowed to be hacked, kdog316.

As Amy said, they'd most likely be hacking the vB3 on their test boards, usually offline. :)

[Freddie Bingham]

Today at 06:57 AM amykhar said this in Post #8 (https://vborg.vbsupport.ru/showthread.php?postid=389377#post389377)
What concerns me is that some of the beta testers might be "converting" the work of existing hacks and then releasing them as their own work because they have the jump on timing, having had the code for so long.

Amy I'm sure if such things were to happen, the hack police would be on the job to arrest them when they posted.

Also, I don't think we gave the private beta to many people that we felt might feel inclined to modify the source code. Modifying the source code only hinders our ability to distinguish real bug reports.

[filburt1]

Today at 11:10 AM assassingod said this in Post #10 (https://vborg.vbsupport.ru/showthread.php?postid=389391#post389391)
I dont think beta users were/are allowed to edit the code in the first place?:confused:

The private beta testers aren't but there's little Jelsoft can do to control the public beta.

[Xenon]

while vb3 is in betatesting (also public)
we won't have an hacking section here, so private testers won't have an advantage on hacking, except they know the code a bit better ;)

also if someone sees his own hack ported by another one, just call us

law and order is within our board ;)

[PixelFx]

sounds good,

once vb3 is out, will you guys have a new vbulletin.org setup for that or use a sub domain off tis site for hack addons ,,, general question... This is when it goes public for licenced members, is what I'm asking about ;) did that make sence? I'm thinking I need more sleep :P

[filburt1]

The plan is undecided (and classified) at this point but will involve supporting both vB2 and vB3 for a while as well as changes to the hack db and possibly the hack submission process.

[Xenon]

like our Turtle said, it's not completle fixed what we'll do exactly.
We will also upgrade to vb3 and have to see how we can use some new features for vb.org improvement.

vb2 will be supported as long as enough people here will hack it ;)