oponent does not respond and then i lose

[ginandtonic]

I just played PVP for the first time in months (because it is so buggy).  In the very first game I played I was well ahead and the opponent timed out and I got 'disconnected' from my very reliable internet connection and was given the error message that my connection was lost and I was going to lose in 9...8...7... and I could do nothing and lost the game when the counter reached 0. 

Since its inception, I have donated money and I don't run ad-blocker for this particular website to try and support this great game.  Sorry to see it going down the tubes. 

[timetock]

It's gonna be ok people just don't play PvP or play it fairly. And if you're one of those goddamn cheaters just know that karma is out there to get you. And you will suffer for those crimes YOU SHALL PAY

[shabr]

at first it said "your oponent is not responding the cpu will take over in 10 seconds"  and when it had around 2-3 seconds to go it changed to "your connection to the server is not responding you are going to lose this match in (it said 2 so i asume it takes the timer from the "oponent not responding" message) seconds"

the second counter starts from beginning(7 sec i think) for me. So sometimes when the difference between disconnects is big enough, The opponent AI plays the hand And I manage end my hand before "your connection to the server is not responding you are going to lose this match" counter goes to zero. Happens very seldom, but after that I can finish the match successfully. Maybe it helps in identifying the problem.

PS. I have not been playing for about a year. Back then I did not have a sigle disconnect from my side. ISP have not change.

[Jyiber]

I've quit pvp. Hopefully this is fixed when Zanz rolls out 1.4.

[Submachine]

I've quit pvp. Hopefully this is fixed when Zanz rolls out 1.4.

Hopefully Zanz even remembers this game.

[dawn to dusk]

I've quit pvp. Hopefully this is fixed when Zanz rolls out 1.4.

Judging by the rate of 1.4, hopefully it is before then.

I was definitely one of the earlier people to get effected in this patch but I disregarded it as I didn't see this as it was so old and I knew my Internet connection was laggy at times anyway. But seeing how much this has progressed it amazing. I when I first saw it, it only happened in PvP1 (so I decided to farm PvP2 with semi-upped adrenastaves) but the amount it has spread... It makes the PvP badge on kong impossible to get...

[Jyiber]

Yeah it's interesting how it's spread out. Just watching Troubleshooting and Bugs threads I've seen it go like this:

It started out only affecting some people in pvp1.
then more people reported, but it was still fairly isolated.
Then it moved to affecting pvp2 and dual...
...and now it's affecting many people in all pvp.

I was also effected by the early forms of this problem.

[andretimpa]

I've quit pvp. Hopefully this is fixed when Zanz rolls out 1.4.

Hopefully Zanz even remembers this game.

Yup. The "birthday" of 1.32 is approaching and still no update ...

This pvp bug is just the cherry on the top

[Zso_Zso]

The way it spreads and gets more and more frequent as well as the fact that it is still somewhat random and not tied to any specific sequence of events makes me believe it might be some kind of memory leak related problem on the server which keeps getting worse as it is up and running. If my suspicion is true, a simple reboot / restart of the server would "fix*" the problem for a good while.

*: of course, its not a real fix, that would require fixing the memory leak in the code, but a regular reboot would make the problem disappear from all practical aspects.

[TribalTrouble]

The way it spreads and gets more and more frequent as well as the fact that it is still somewhat random and not tied to any specific sequence of events makes me believe it might be some kind of memory leak related problem on the server which keeps getting worse as it is up and running. If my suspicion is true, a simple reboot / restart of the server would "fix*" the problem for a good while.

*: of course, its not a real fix, that would require fixing the memory leak in the code, but a regular reboot would make the problem disappear from all practical aspects.

If only this worked for when Zanz got a memory leak about how he's supposed to work on Elements… -_-'

[Jenkar]

Except he's not "supposed" to. :V

[TribalTrouble]

Except he's not "supposed" to. :V

Shhh. He might not know that!