Hack Properties: Min / Max vB Version

[akanevsky]

The questions like "does this 3.6.0 hack work with 3.6.1" are never going to end, unless... you guys implement a minimum / maximum vbulletin version properties. What you say?

[RedTyger]

Isn't it easier to just update a hack's version? I don't do it as soon as vB release a version, but if I've visited a thread to read the question it takes 10 seconds to do it while I'm there.

[akanevsky]

Originally Posted by RedTyger

Isn't it easier to just update a hack's version? I don't do it as soon as vB release a version, but if I've visited a thread to read the question it takes 10 seconds to do it while I'm there.

No, because the question will then change in the following way:
"Does this 3.6.1 hack work with 3.6.0?"

[Marco van Herwaarden]

The problem is that an author will fill out the info when he releases the modification, and at that time he does not know yet until which version it will work.

Nothing is stopping an author to add a text "This will only work until x.x.x" if he wants.

[akanevsky]

The problem is that an author will fill out the info when he releases the modification, and at that time he does not know yet until which version it will work.

Yes he does, at least if he releases the hack using the latest version of vBulletin available. (and why would he do otherwise?).

[Marco van Herwaarden]

But he does not know when the next vB version will be released, what it will be named/numbered or if his modification will still work on that future version.

[akanevsky]

Originally Posted by Marco van Herwaarden

But he does not know when the next vB version will be released, what it will be named/numbered or if his modification will still work on that future version.

Why would someone be concerned about a future version that has not yet come out? When it comes out, the author can update the hack properties.

[Marco van Herwaarden]

If the author wanted to do that, he could already edit the description and place a line saying "This will only work until version x.x.x".

Since i don't see anyone doing that, i am assuming that it wouldn't be updated if there was a special field or it either. And if there is a field for it, but it is let empty by the author, then a reader would asume that it is still working for the latest released version.

[akanevsky]

Originally Posted by Marco van Herwaarden

If the author wanted to do that, he could already edit the description and place a line saying "This will only work until version x.x.x".

Since i don't see anyone doing that, i am assuming that it wouldn't be updated if there was a special field or it either. And if there is a field for it, but it is let empty by the author, then a reader would asume that it is still working for the latest released version.

Coders do not do that (or at least I do not do that) because I believe that users do not bother reading through the long introductory posts. They obviously do look at hack properties though since their questions are based on that.

It is not necessary to allow to leave the field blank.

[evenmonkeys]

It's also possible that a modification would work for 3.6.0, 3.6.1, 3.6.4... but it doesn't work for 3.6.2 and 3.6.3. So this wouldn't really work well in that situation. In any case, people will always ask questions that are easily answered by reading the first post; or even reading the title of the thread. I like the idea, but it wouldn't fix every related problem.