team balancing

[Sammy]

Ok. So… that means auto balance wasn’t it. But, half time again. So that is the next possibility to investigate. Also after sudden death? Not a tie. And I noticed at least two people leave.

thx.

[Totty]

37 minutes ago, Sammy said:

Ok. So… that means auto balance wasn’t it. But, half time again. So that is the next possibility to investigate. Also after sudden death? Not a tie. And I noticed at least two people leave.

thx.

Yes the issue usually happens at half time, 

We definitely have been getting fewer crashes since the auto balance was moved, so still might be a factor somehow 

[Sammy]

Starting with the assumption of it happening at halftime. Different vids iirc also establish, under this assumption, that the winning/losing score can be any variation of four rounds. 2-2, 3-1, 4-0.

Next is whether or not sudden death happens every time and never after regulation play, so to speak.

edit: ‘usually’ is an important distinction.

Edited September 18, 2023 by Sammy

[Totty]

1 hour ago, Sammy said:

Starting with the assumption of it happening at halftime. Different vids iirc also establish, under this assumption, that the winning/losing score can be any variation of four rounds. 2-2, 3-1, 4-0.

Next is whether or not sudden death happens every time and never after regulation play, so to speak.

edit: ‘usually’ is an important distinction.

I do not know of a time that it didn't happen in overtime/sudden death

[Sammy]

Ok thx. Anything that narrows things down with certainty, or rules things out, helps trace and step through all the relevant functions.  Especially when it has to all be done by hand instead of running the game through an IDE debugger.

[Totty]

I will try to analyse it more and get as much info as I can

[Sammy]

Going through vids seems its not just at halftime. Was a good thought.

[Sammy]

Hi all. You might have noticed certain extra server lines at the bottom when the round ends. It is for helping to step through the various events and see what happens. Hopefully it will be useful if this happens again. So if it does, plz let me know what it says. Looking for something about score limit, round limit, or tie games in particular. Also if the 'winner' is a team or a player.

If the winner is a player it suggests the game ended early but as a tie game. When that happens in team games, and there is no team winner, the scoreboard shows everybody based on their player scores. It also doesnt play the usual 'won/defeat' dialog and music. So this suggests something is forcing a tie game early. 'Force end' is a normal flag that tells the game that it is over. Could be score limit. Could be a forfeit.

Edited September 19, 2023 by Sammy

[Bamm]

We just had one again:

Our team won this round and I believe we had red bubbles if I remember correctly? In case it matters. I didn't pay attention to the score again though nor did I notice if it was halftime or not. I asked the other players, Kamikaze thought the score was 2:1.

[Bamm]

In normal map ending where red won 4-0, it also said that winner was axis:

 

Only thing that confuses me is that the code says score limit reached before the code says that the last person was shot.

[Sammy]

The second one, the console screen is scrolled too far up to see current data. Sometimes the print statements are not in order. Or in this case the obit. However the data on the first one is interesting and unusual.

[Bamm]

16 hours ago, Sammy said:

The second one, the console screen is scrolled too far up to see current data. Sometimes the print statements are not in order. Or in this case the obit. However the data on the first one is interesting and unusual.

With the second one, we already went on to the next map, so the map you see behind the console screen is the next map. The data that came next was all about the changing maps/getting the new map. So I think it was the relevant info of the previous map ending? I'm not sure what obit is though. And as reminder, second screenshot was of a normal map ending.

But I'm glad the screenshot of the actual error is helpful in a way

[Sammy]

obit = the player-gunimage-player line when a player is killed. obituary.

Made a couple changes to simplify a couple checks and how round and scores are kept. Since people are playing I am assuming it didnt shit the bed.

[Bamm]

No early endings since you made the final changes. At least not yet.

[Sammy]

Thx.

[Bamm]

Okay, we had a weird new error, but I'm quite sure it's related.

So we were playing, blue team won a round (I believe from overtime), should have been 2-3. Instead the game turned it to 2-4, but didn't end the game and let us play another round. It did start spamming error messages every second to multiple times per second:

These were the error messages:

Showing the 2-4 score while still playing (screen is red because I'm frozen, actual score = 2-3):

Sadly, before I remembered to take a screenshot of the logs when it went wrong, the error messages already spammed too much and erased it all.

[Bamm]

We played on despite the constant error messages. That next round we won (red), so should have been 3-3, but of course still said 3-4. The game ended at that point anyway, saying WE (red) won, despite showing the score 3-4. It ended without yellow screen.

Logs of final round ending:

[Bamm]

Hmm my messages make the pics less clear.

First pic with the error says: Server g12605: checkScoreLimit () - One or the other team has reached the score limit. goto level.onScoreLimit

That error was spammed for the entire next round.

Final pic says the error messages still, but also:

endgame called by ftag ongameended. Team != all
error message ^
Serverg11811: Send game_ended notify
Server 1901: forceEnd is set to false or is undefined. Rounds played is 6
Server g12083: Game is over. endReasonText - Score limit reached. Winner - axis
Server g12142: Play EOG music.
Server g14103: announceGameWinner is a team. Winner is axis

I'm guessing the announced winner is always seen as the team that won the last round and that's why our team won despite the 3-4 score. Because usually the winning team will always win the last round.

[Totty]

we had a strange event earlier, we were 2-3 and just won the round to get to 3-3 and this message apeared for the entire next round

this was probably taken too late for you

At the end of round we won and should have been at 4-3

 

[Sammy]

Ok thats an unusual one. Do you know the name of the 3-3 map?  Do you recall what it said at the beginning of the map how many rounds are needed to win?

edit: novoutpost?

edit: Checking things there was a match where the listed number of rounds played is one more than the sum of the scores. But maybe there was a tie game along the way, which would count as a round played. One of the debug messages will show this at the end of the round to see if that variable matches the actual score.

Edited September 30, 2023 by Sammy

[Totty]

Ok, I've knocked a video together hopefully giving you more info than I can,

Round 1 ended 1-0 No sudden death

Round 2 ended 1-1 With sudden death

Round 3 ended 1-2 No sudden death

Round 4 ended 1-3 No sudden death

Round 5 ended 2-3 With sudden death

Round 6 ended 3-3 With sudden death

Constsant error scrolling through Round 7

Round 7 ended 5-3  No sudden death

Screenshots above were from round 6 and round 7

[Bamm]

4 hours ago, Sammy said:

edit: Checking things there was a match where the listed number of rounds played is one more than the sum of the scores. But maybe there was a tie game along the way, which would count as a round played. One of the debug messages will show this at the end of the round to see if that variable matches the actual score.

 

20 hours ago, Bamm said:

Final pic says the error messages still, but also:

endgame called by ftag ongameended. Team != all
error message ^
Serverg11811: Send game_ended notify
Server 1901: forceEnd is set to false or is undefined. Rounds played is 6
Server g12083: Game is over. endReasonText - Score limit reached. Winner - axis
Server g12142: Play EOG music.
Server g14103: announceGameWinner is a team. Winner is axis

 

So with the event where I was present, it says rounds played is 6 in the console (which was true), but our final score was 3-4, which should have been 3-3 at that point. The error where it counted an extra point was in the round before the final one.

[Sammy]

Well thats weird. If I am seeing things correctly, at the end of round 6 (3-3) and the standard things, after doing the halftime part it also seemed to trigger at least one of the end of round functions again. Which in this case looks like it probably does add one more to the team that won(?) the last round. 3-3 shows 4-3. Visually.

However if I am interpreting what you posted correctly, while the screen shows 5 to 3 at the end, the actual results and score was correct as 4 to 3 and 7 total rounds played. The victor is declared and game over.

edit: For info, round 7 is halftime.

Edited October 1, 2023 by Sammy

[Bamm]

23 hours ago, Sammy said:

Well thats weird. If I am seeing things correctly, at the end of round 6 (3-3) and the standard things, after doing the halftime part it also seemed to trigger at least one of the end of round functions again. Which in this case looks like it probably does add one more to the team that won(?) the last round. 3-3 shows 4-3. Visually.

However if I am interpreting what you posted correctly, while the screen shows 5 to 3 at the end, the actual results and score was correct as 4 to 3 and 7 total rounds played. The victor is declared and game over.

edit: For info, round 7 is halftime.

Seems correct for that one. However, incident where I was present it wasn't halftime yet I think? So I'm talking about this incident:

 

On 9/30/2023 at 2:20 AM, Bamm said:

Okay, we had a weird new error, but I'm quite sure it's related.

So we were playing, blue team won a round (I believe from overtime), should have been 2-3. Instead the game turned it to 2-4, but didn't end the game and let us play another round. It did start spamming error messages every second to multiple times per second:

These were the error messages:

Showing the 2-4 score while still playing (screen is red because I'm frozen, actual score = 2-3):

Sadly, before I remembered to take a screenshot of the logs when it went wrong, the error messages already spammed too much and erased it all.

 

 

The error happened after we played 5 rounds, going to the 6th. The team that won indeed got the extra point. Map was mp_matroska

Edited October 1, 2023 by Bamm

[Totty]

On 9/30/2023 at 8:49 PM, Totty said:

Ok, I've knocked a video together hopefully giving you more info than I can,

Round 1 ended 1-0 No sudden death

Round 2 ended 1-1 With sudden death

Round 3 ended 1-2 No sudden death

Round 4 ended 1-3 No sudden death

Round 5 ended 2-3 With sudden death

Round 6 ended 3-3 With sudden death

Constsant error scrolling through Round 7

Round 7 ended 5-3  No sudden death

Screenshots above were from round 6 and round 7

It showed as 3-3 at the beginning of round 7 and jumped to 5-3 at the end of round, which should have shown 4-3