Please elaborate
First off IF you get disco two things happen:
A.) your plane gets shot down and you start back in the tower when you reconnect. Still a death regardless if you reconnected with or without this option.
that statement shoots itself down...if ending up in tower is the end result regardless of fix/no fix, then there is no need for htc to spend countless hours undertaking the monumental task of trying to code it properly, and address all the whines about it not working the way some know it all thinks it should...as there is no benefit one way or the other
B.) your in your B29/262 and you get a disco while climbing out to altitude. You have the ability to reconnect and pick up where the autopilot has taken you in the time since you lost connection.
I do NOT see how this can be a bad thing. Please tell us. Enlighten us. If you can bring up legit problems with this I will reconsider my position.
i'm just gonna take a guess and figure you don't understand the difference between an instance where the disco does not shut the game down and the object the client system was attached to comes to a dead stop...and an instance where the disco shuts the games connection to the server down completely and the object one was attached to does not remain stationary and forces the need for more information to be passed between the client and the server which puts a larger load on the server since every single client attached to the server (200 - 300+) has to be tracked...unless the toon gets shot down, then all the calculations get terminated until the client reconnects...
think server load, lag, bigger data streams, more instances of discoes...this "fix" goes beyond the end of ones nose
again...wot - 30 players max per battlefield
ah - hundreds
wot - tank stops on a disco
ah - can't stop a plane in mid air (unless you really want htc to code it that way)
wot - disco does not kill the game and disconnect the client system completely
ah - disco causes complete shutdown of game and connection forcing a restart
