I see. Well, I'm glad we do have a rating system, Forged Alliance (under GPGnet) did not have anything. I was not aware it had that many problems. Thanks for explaining it.

Hi,

this is a new issue where the game cannot kick observers (when I try by hand, it does not work), the game then hangs forever with the kick observers? dialog visible and crashes.
This has worked before, so it is a regression bug, anybody else struggling with this?

Another possibility is also to ask the observers to leave on their own before the game starts. So why did this bug come back? I personally never had this, ever and I was one of the original players that bought Forged Alliance back when it was brand new.
Can you guys also keep the debugging switched on so you can submit the logs? Where should we submit the collected logs?

No, that is a bug: I know from experience that you can use arty to defeat an enemy in that position, I have done it before and, if you look at the replay, I built arties that were a little further away, they did fire actually, also: You are aware that PDs as well as missiles, as well as arties will happily fire into a mountain or terrain if that is in the way?
Cruisers will fire into mountains if this phenomenon of height difference comes into play, also:
Arties fire in an arc, they can actually fire against something that is on an elevated position. This makes the elevated position on the back almost indefeatable, because you can't use missiles, you can't use arty, you can't walk up there, if you make sure you make all air impermeable, then nothing can touch you, nothing can reach you, but the enemy can shoot everything in the base without opposition, very odd and unbalanced.

Ah ok, so these sizes of logs are totally manageable and not huge, I will keep the debugger on to capture logs.

Question: How much does having the debug logs on impact performance? I know from my IT experience that gigabytes and gigabytes of logs can be generated, depending on the verbosity level.
Can I leave the debugging on? I just run into a bug where the T2 stationary artillery will neither aim nor fire, won't even turn, totally bugged and the whole game being affected (several players)

Replay code:
23033384
on the right side, bottom.

Bugged T2 Arty does not aim or shoot, even when commanded, bug happened for 2 players (one of them CaipirinhaPilot)
We had somebody take up position next to our base, his arty was shooting, ours was not. His missiles could hit us, ours crashed into the mountain (that is fu**ing unfair)
We built probably 15 T2 arty that did not aim or even turn, no firing, this is a regression bug, never had this before.

Ok, I will switch on the debugger, that should create more verbose logs. I read about the issue in a post, I did not even know if it was caused by kicking observers and so I tried to kick the observers before hosting the game and it worked with 2, but one of them, it did nothing, the kick function just came back with no result. Then when starting the game, exactly the effect and crash that @SainseRow described. So I let a friend host a game and he could neither kick certain players. I will check the lobby state, is there something specific that I should be looking for?

Hi,

this is a new issue where the game cannot kick observers (when I try by hand, it does not work), the game then hangs forever with the kick observers? dialog visible and crashes.
This has worked before, so it is a regression bug, anybody else struggling with this?

Is it hanging after it tells you that you have to kick players and you say yes? If yes, I and a friend have the same issue, it is related to not being able to kick players.

I see. Well, I'm glad we do have a rating system, Forged Alliance (under GPGnet) did not have anything. I was not aware it had that many problems. Thanks for explaining it.

Global what? Which problems?