Aces High Bulletin Board
General Forums => Wishlist => Topic started by: Ack-Ack on November 13, 2012, 11:31:26 PM
-
The title says it all. I wish that WEP would be fixed when returning to flight after being discoed.
ack-ack
-
What happens to WEP after a disco? :confused:
-
I think that's actually a bug/glitch ak :headscratch:
-
I think that's actually a bug/glitch ak :headscratch:
Which is why I wish it would be fixed.
ack-ack
-
What happens to WEP after a disco? :confused:
No WEP.
ack-ack
-
Which is why I wish it would be fixed.
ack-ack
Right, but I was thinking this thread might belong in the Bug Reports? Eh, it doesn't metter, and who cares *shrugs*
+1 ! I hate coming back to no WEP, especially if I just rolled :furious
-
Right, but I was thinking this thread might belong in the Bug Reports? Eh, it doesn't metter, and who cares *shrugs*
+1 ! I hate coming back to no WEP, especially if I just rolled :furious
It's been posted in the AH Bug Forum but so far it still exists so I'm wishing for this particular "glitch" be fixed.
ack-ack
-
The title says it all. I wish that WEP would be fixed when returning to flight after being discoed.
ack-ack
I suspect (assuming I know anything about how it's actualy done) the way it's currently done is because all "max WEP time" and WEP cooldown (and thus ultimately engine management/temperatures) are managed/kept/stored on the client side (which just crashed/disconnected and thus lacks an exact or close-enough idea of what your true engine/WEP state was before disconnecting).
The easiest way around it would be taking the "maximum WEP time" variable (and maybe a new variable or two) currently tracked client-side (our machines), and then sync that continuously to a server-side tracked variable per player (on HTC's machine). Upon disconect, it retains the last updated value(s) for ~5minutes. When reconnecting, it retrieves these variables (IE: WEP time, was WEP on/off, time of last update (to calculate if WEP was left on during disconnect and how much since reconnecting was exhausted).
Doable, and I would like to see it too, but maybe not easily. Only HTC's knows. It is annoying to be conservatively managing your engine, a few minutes out from a fight, then disconnecting and returning still imminently from the fight (or already there), and your conscious engine/WEP conserving goes out the window.
-
So some dweeb can pull the plug when wep runs out and then replug and get wep back... Um NO!
However if you haddent used all your wep and "discoed" then ya get what time you had back +1
-
HiTech said it is intentional and not a bug
http://bbs.hitechcreations.com/smf/index.php/topic,338868.msg4469420.html#msg4469420
Don't know why though.
-
HiTech said it is intentional and not a bug
http://bbs.hitechcreations.com/smf/index.php/topic,338868.msg4469420.html#msg4469420
Don't know why though.
As I tried to explain, it's because the "How long has WEP been running/used" variable/number that is being watched by the game for when you've used it all up is most certainly tracked/managed/watched/governed by the client-side of AH (what's running on your computer). When AH crashes/disconects on your computer, this number is lost to the nether. Thus, when you reboot or reconnect, the server or client side with AH doesn't have any idea/memory of how much WEP you've used.
So, what is the best choices from this point? As it currently is - which is to set the "how long has WEP been running/used" value to max/pegged, thus requiring you to then wait for the amount of time defined by the "how long does it take for the WEP-used variable to reset-to-zero/recharge/engine-cool-off", a defined amount of time within the game for each plane. Or, they could reconnect with it fresh/unused/0, but -
So some dweeb can pull the plug when wep runs out and then replug and get wep back... Um NO!
However if you haddent used all your wep and "discoed" then ya get what time you had back +1
Definetley exploitable for abuse by players.
There is a third option though, but I already tried my best to explain that a couple posts up. (three aditional numbers/variables would need to be tracked by the server and kept safe/unmolested on it in the event you disconnect and then reconnect in flight. First being the "how much/long have you currently used up your WEP time", the second being "was WEP on/off when you disconected" and the third being "what time you diconneted". When you reconnect, these numbers get looked up and depending what your current state was, if you were useing it up or lettign it cool off, and how much was used up or cooled off since your disconnect and reconnecting.)