Digital Paint Discussion Board
Development => Bugs, Feature Requests, and Feedback => Official Feature Votes => Topic started by: KnacK on May 05, 2008, 03:08:04 PM
-
Why do we need backward compatibility?
How many features or enhancements are we missing because of backwards compatibility.
I propose getting rid of backward compatibility in order for Jits to exercise enhancements, fixes, and features, that might not be possible if we maintain a 100% backward compatible client and server. ( yes, this goes for server too)
-
Darn, you beat me to it. :P
-
;D
-
I like the idea. If we could have just one new release that is no longer backwards with the previous builds, only good things can come.
-
Well before this happens servers are going to have to put a message up because I see people connecting with Build 16 still....
-
I'm pretty sure the 'You can't connect anymore' will be their wakeup call.
-
Hell yes, i so agree, the game can have so much more enhancements without backwards compatibility.
-
A benefit: If this means people on old clients can't connect anymore, we can say goodbye to ZGH and Penix!
-
trust me they will get new clients
-
I believe penix was designed to work with quake 2, and ZGH people aren't able to login meaning they're still on an old build. So, unless you're going to make some, that's some cheating out.
-
why dont they get new clients rather than stick with the old
-
I don't think you understand: I'm saying this would be a benefit, because people who use wallhacks like ZGH and penix will no longer be able to play.
</excessiveUseOfItalics>
-
oh yea, i forgot those were hacks. come to think of it, if we break backward compatibility we can have a hacker firewall sorta thing (which never would be possible)
-
sounds like plan... or backward compatibility to the last 3 builds only...
-
sounds like plan... or backward compatibility to the last 3 builds only...
That'd be a pain to keep track of. I think it'd be best for the development of this game if backwards compatability was disregarded entirely. If it works with the old builds, great, but that's not the goal.
-
so.... are we trying to get people updating to latest version? cause i thought the point was to get rid of people using older clients like build 16 and force them to use the latest one...
also, is it not possible to get a "detect" function on the server side to detect minimum build requirement?
haha, i like the idea of "you can't connect anymore because the version you're using IS TOO FRIGGIN' OLD!!!!" :D
-
This will be fun getting servers to be updated every build.
-
Yep. Denying older uses access just for the sake of denying them access isn't justified at all, but I don't think progress should be held back because some people are too lazy to update their builds.
-
Picasso will be on his feet then. Doubt Snipen will bother to update them :P. Can't wait for Build 21 on the GT Servers. Warmup Mode.
-
i just hope we get rid of all this EVENTUALLY
-
sv_minclientbuild.
-
sv_minclientbuild.
???
-
but not with map formats...
-
sv_minclientbuild.
That's all fine and dandy but you will still have those server admins that won't do this.
But if you are *fine* with this, and you don't think it will restrain you from advancing the game, then it is ultimately your decision.
-
i think i'll give a +1 for this.
for any that might be against breaking backward-compatibility, i would draw your attention to the fact that technically, this game is still classified as in ALPHA, the stage of program development where all the serious work gets done, where ideas come and go, and things change - a lot. as such, i don't think breaking bw-cmp is a bad thing.
-
Jits,
If backward compatibility were not an issue, could you implement new features or improve existing features?
Or, asked another way, is backward compatibility hindering the advancement of the game?
-
I think it might be more of a hindrance to abruptly remove backward compatibility. If nobody could connect to new servers with the old clients, the servers wouldn't update, and if the servers aren't updated, nobody will want to use the new client because they can't connect to the old servers. There would always be rough transitions which would severely decrease the player base. It would also mean I couldn't test the new client on old servers or update my test servers with the new version as none of the current clients could connect to them.
-
true, true, and i'm not saying keep compatibility strictly to the latest version only ... i don't think older clients should be disabled just for the sake of doing it... but if advancement of the game would break, say, clients of build 18 or earlier, that might not be something to worry about too much... as they should be more up-to-date than that.
like knack indicates, bw-cmp is only an issue if it impedes development.