Autodraw desync games for CW and CF

[nabo.]

@neco any news? interested in solving/minimizing desync issues?

[Neco]

I've been working on it for the past week, and have been learning a lot. Need to run more tests before I have a solution though.

[SirSandgroper]

Hi, often de-sync happens due to late round lag (I'm talking Castle Fight). If red sets the mode to -gld25 to -gld27 or so, that can minimise chances of late game lag and subsequent d/cs. That atleast minimises the chances of d/cs via that way. I'm not remembering clearly if that's the main way most are d/ced but it's amongst the most frequent?

So shorter rounds and shorter games. Long rounds and long games - will naturally lose players due to d/c and/or boredom/real-life taking hold.

In regards to the proposal - seems a good idea to me, only fair? From experience some have refused to draw in unfair circumstances, so this would be good for that. But I've also played with many fair types, usually many familiar faces old pros and fair newbies who agree to !draw in games where they've skewed really unfair due to drop-outs, long-time afkers or something like that. Games where votes aren't decided can drag on longer and be less fun for all involved and even ironically lead to more drop outs, so it's better for all if this kind of resolution instigated?

[supersexyy]

Dc and desync are two different things, I think you're confusing them.

[aRt)Y]

I've been working on it for the past week, and have been learning a lot. Need to run more tests before I have a solution though.

@Neco bump.

[Neco]

I've been working on it for the past week, and have been learning a lot. Need to run more tests before I have a solution though.

@Neco bump.

The new Sync code is in the latest ID beta. Once I get it into an autohostable state we'll be able to monitor the result to see if it improved anything.

[Neco]

Looks like the problem stems from the W3MMD system itself, rather than the act of syncing.

Might have to try and rewrite the library...

[OVanKillerratO]

Concerning CF:

Autodraw might be better than useless losing games while winning. But I've seen many games in which someone of the losing Team seemed to have pulled out his cable or deactivated w-lan, just to avoid losing, and sometimes even get a win. autodraw could be abused easily, to save your elo when losing. Better would be if it was possible to check the roundstats (won rounds per Team) and make a autodecision based on that. desync occurs mostly after votekicking and leaving, or votedropping after a round, so there should be a possibility to check how many rounds a Team has won.

[nabo.]

@Neco

news?

[RaptorXI]

It's up to you but... is there a section where mappers and developers could work on those technical issues? I've made a version that could be uploaded on Ent16, so far only balancing to reduce complaints by pros, the instablity problem remains.

[aRt)Y]

Off topic:
@RaptorXI https://entgaming.net/forum/viewforum.php?f=27

[F-Train]

By far the most common reason for desyncs is the misuse of GetLocalPlayer()

[OVanKillerratO]

Are there any News about what will happen with desync games? it really is a Problem in Castle fight.

[nabo.]

@Neco guess we wont be expecting something soon.

@uakf.b autodraw CF CW desync games?

[Neco]

I've pretty much confirmed at this point that the desync occurs from the design of the MMD system itself. There are alternatives but it's a slow and gentle process.