Major Time Race issue that needs to be resolved before TWL starts

[Jason]

Stop using the word jupe.

[Verthanthi]

If someone already slammed into it, why did I see it as blue? Anyway, this is moot because it'll be fixed.

[Sufficient]

You got JUPED! ... haha I like that word. Let's all use it now. I remember one basing game that got juped ...

[Pio]

Well this is pretty weird because the bot recieves reliable packets, meaning if the zone sees the flag as being owned the bot will recieve the packet as the flag being captured. But then again, maybe not.

[PaulOakenfold]

Juped = the new Served (since that's being over used now)

[NaiLed]

stop saying juped sins!

[Mythrandir]

It never used to be such a big issue before, because the server would still record the right number of points even if you lag died on the flag. But with these MatchBotR Time Race games, it is crucial that the bot knows exactly which team has the flag at ALL times.

It has always been an issue, because the server uses the exact same information as the bot does. The difference is that people notice it nowadays since they're much more focussed on the flag than before, which results in more people rushing for the flag.
So, TWLB can start with this issue as much as it has been the many seasons before.

The actual problem is not with the bot, but with the Continuum client (that's what I assume). Because the client changes flag-ownership based on two different factors:
1. When a player 'captures' the flag, he sends a 'Flag claimed' packet to the server, then the server broadcasts this packet to all other players in the arena. Also once every so many seconds (I think it's every 60 seconds) the server sends a flag update packet, telling what frequency is owning the flag. This is the correct way to determine flag ownership, and this is what the bot is listening to as well.

2. but there is another way. When player A sees player B run for the flag. But player B dies on his way to it, then the following might happen: player B dies right before he touches the flag, so player B won't be sending a Flag Claimed packet. But on the screen of player A he sees player B touch the flag anyway (because of the few hundreds ms lag). The continuum client assumes that player B touched the flag, and changes the color of the flag before actually receiving any flag claimed packet from the server.

[Pio]

2. but there is another way. When player A sees player B run for the flag. But player B dies on his way to it, then the following might happen: player B dies right before he touches the flag, so player B won't be sending a Flag Claimed packet. But on the screen of player A he sees player B touch the flag anyway (because of the few hundreds ms lag). The continuum client assumes that player B touched the flag, and changes the color of the flag before actually receiving any flag claimed packet from the server.

This seems pretty silly that the Client would do this _on it's own_. It should only act when it recieves the packet. Maybe it'll get fixed, i doubt it though

[Dabram]

Another reason why pointrace is so much better than timerace.

[Zerzera]

Uhm.. it doesn´t make much difference now does it. It´s how Camisade lost to Disoblige in last TWL too. So no matter what game-format you use, it will have quite the same effect.
Only now some people are hyped over touching the flag so much they do stupid things.

[Force of Nature]

Uhm.. it doesn´t make much difference now does it. It´s how Camisade lost to Disoblige in last TWL too. So no matter what game-format you use, it will have quite the same effect.
Only now some people are hyped over touching the flag so much they do stupid things.

Wow, someone who actually knows what they're talking about good stuff

[PaulOakenfold]

Another reason why pointrace is so much better than timerace.

How so? That just means the same thing will happen, but with points instead of time. Example: Last year Diso vs Cami (not point race, but point based)

[Stabwound]

I am sure that in the regular 20-30 minute games, if this happened, the MatchBot still recorded the points correctly. The flag turning blue randomly still happened but wasn't really the same.

[Zerzera]

Nope, it's a server/client issue, not a bot-issue.

[Mythrandir]

I am sure that in the regular 20-30 minute games, if this happened, the MatchBot still recorded the points correctly. The flag turning blue randomly still happened but wasn't really the same.

did you even bother reading my post?