Forums » Bugs

Lagged mines test and possible fix?

Apr 13, 2004 Arolte link
Tonight I got some weird lag on my end so I decided to spend a little time to test lag mines out. I got in a Wraith in s9 station and asked others what they observed as I dropped individual mines from outside the station. During the first round of mines I somehow managed to lay five lightning mines using only a single lightning mine launcher. What happened was my last mine didn't count and the inventory still read as one more mine left. So I decided to try again and for some reason it let me lay down an extra mine. After a long time of invulnerability, those mines were eventually destroyed by the players outside.

I continued this for a couple minutes to see if I could get the mines to move by themselves, as I had seen before. I couldn't. But all sorts of erratic behavior occurred with things like excessive proximity radius, invulnerability, ammo count, etc. So clearly some of these reported anamolies are connected with the miner lagging badly (in this case me). So here's a question. Would it be possible to give the server or sector ownership of the mines once they have been placed? That way that can't be lagged.

I can understand that the initial placement of the mines can be problematic, because the server will have to wait for the lagger's computer to send out the information that a mine has been laid. So during that limbo the server can treat it as if no mines have been laid. And once a mine has been confirmed, the server could perhaps take over from that point on as to how long it stays, who gets damaged from it, etc. Or does it already do this? I don't quite get how something that stands still and has two modes (destroyed and not destroyed) could be such a problem with lag.
Apr 14, 2004 a1k0n link
Yes, that is the obvious, and planned, fix, but we won't have time to even look at that until the end of this month. We'll see.

Clients are presently responsible for detonating mines and starting/stopping lightning blasts, which is obviously exploitable.