Jump to content
Come try out our new Arcade we just put up, new games added weekly. Link at the top of the website ×

Bamm

*** Clan Members
  • Posts

    119
  • Joined

  • Last visited

  • Days Won

    2
  • Donations

    0.00 USD 
  • Points

    2,216,750 [ Donate ]

Everything posted by Bamm

  1. In the video we only see the score at the end of round 6, do you remember pulling up the score screen during round 7? Is it possible that it already changed to 4-3 during that round and only added the final point at end of round 7? That would explain the error message and it would be similar to what happened in our map/instance.
  2. 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: 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
  3. 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.
  4. 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.
  5. 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:
  6. 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.
  7. No early endings since you made the final changes. At least not yet.
  8. 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
  9. 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.
  10. 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.
  11. With EOG autobalance, you mean the time where we see 'autobalancing teams' on the screen? I was distracted this time, so no clue if that was going on before it happened. But will try to keep an eye on that as well. I haven't really found a pattern in it either.
  12. What I just noticed by the way, in both my instance as in Totty's Typhoidzilla just left the game. I say we blame him Weird coincidence, but the leaving of the player might be the problem I guess? Or speccing like I did now, you can't see that in the logs.
  13. It just happened again: I'm not sure if the count was 3 to 3, might have been. I had just turned to spec from overtime, because my flatmate came in from holiday. I caught the screen and immediately did the screenshot, but I missed what was happening before because of my flatmate. This I could see in the logs though. I'm not sure at which point I turned to spec if that mattered at all.
  14. I think I have seen the yellow screen with early ending of the game once after this was implemented:( I can't remember which map anymore, will keep an eye on it next time and try to make a screenshot as well if it happens
  15. Bryan isn't correct though Should be this: I don't believe he ever eats anything else
  16. Excuse me, Mrs. Rockstar, I still count that as a nickname Great writing pink
  17. So sorry to hear that I missed him in Zoom today and can't hang around longer, but let him know that we're thinking of him and he's missed in game as well.
  18. Open the console by pressing ~ key on your keyboard (top left). Then write /connect and the ip address you want to connect to. Hit enter and you should get connected.
  19. I'm quite sure you're right Totty and it isn't random. At least it clearly wasn't when I wasn't a clan member, so a year ago it worked like that. The more you played in total, the later you got kicked. I don't think much has changed since
  20. But... did you ever see the triple rainbow?
  21. Honestly if only 1 player bothered to vote and apparently the rest doesn't mind, then I would say go with the voting person. If anyone else cared, they should have voted. That's why the voting is there!
  22. Yeah there you are! I just knew this was going on after the other day Perfect guy for the job, so congrats Weedy!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.