Though I am fairly confident that he is a known bad apple, it is also fairly well established that it is unlikely that someone can cause this error to occur.

edit: also, grabbing that last flag has nothing to do with anything.

Yes, py4eek is a know bad apple and you should always refrain from playing with or against him. I am surprised that Jona__ actually did play against him.

I had the exact same situation about a week ago right after Chiefy and I had locked both of his portals. Chiefy said, "Here comes py4eeks invalid gamestate," and Boom, would you look at that, there it was.

Never again.

There are very few 70%-plus players I trust except for the very small handful who I know are actually that good. But that is a short list.

It is blatantly obvious,  he says something about the flags to cover his ass then right after invalid gamestate

Anyone can trigger a desync.  The flag bug does not exist.  A few maintain that it does.  I've done quite a bit of testing with a few others that indicate that the flag bug does not exist. What happens is someone initiates a desync right around the time that all flags are captured.  Its not some bug.  Its someone being a jerk.  You are better off not playing against py4eek as this has happened and been reporting by MANY different people.  Best case scenario, in his defense, you can say maybe he just has bad connections.  Worst case and somewhat probably, is that he's a cheat.  Either way, its best to simply avoid him. 

I'm still not convinced that there isn't a relationship. When testing (also with pacov at one point) there were significantly more server update requests following a capture event then when not following a capture event. Failing these requests may cause desyncs.

had a 1 vs 1 against him....turned out to be a nice player that can take a loss...even against a noob like me....

so....cant confirm what u write here....

I'm not saying that this justifies cheating, but is it possible you were rude to him and that this is why he denies you the win? Judging by my most recent experience with you and by the post about noob-bashing, this is very plausible.

winning isn't synonymous with polite.

News flash.

Me and Ptarth just reproduce flag capping bug over 6 times or so after i reinstaled demigod into russian version.

The bug exists and if anyone want me to prove it to them im idling in pacov vent.

So pyek in not at fault here.

He is. He just knew how to do it.

i just talked with irek py4eek just uses the bug as an excuse we had 4 flags left up just for that reason.  Irek says it only happens when u have all but 1 or all.

Ok - I'm guessing ptarth is going to post something in more detail later, but yes, this bug apparently does exist.  It is reproducible and it is based on map control.  I made quite a few tests with irek to confirm and yup, it happens.  The issue occurs, without a doubt, between the russian and us versions of the game.  That's the reason why I could never reproduce the bug - it doesn't appear to exist in US to US games. 

So - here's the basics on how it happens.

At least 1 user has a US copy of the game.  At least 1 user has a Russian copy of the game.

1 team takes all of the flags.  The other team reclaims 1 flag.  Boom.  Invalid game state.  It seemed to happen almost immediately when the forces of light are the team that is taking all of the flags.  If forces of dark took all of the flags, then light took 1, it didn't always happen immediately.  Sometimes swap the flags a few times.

I tested this with irek using a map that ptarth created that moves all flags to middle of the map.  Once that triggered invalid gamestates consistently, we played an unmodified cataract and the invalid gamestate still occurs (i was light - took all flags, then irek, on dark, took 1 flag). 

So, its reproducible.  As far as a precise fix, something is probably off in the Russian localization file. Its unclear whether or not Russian v Russian games will have the same problem or not (but I'd think so).