Kouki

Okay, a few things to go through here. First off, as Skitso mentioned, symbiotes are currently not counted in the post-GC screen, I'll clarify this and a few other things as I'm not sure whether this was intentional or not. Captured enemies are also not added to the kill indicator (skulls) and it's possible that one of the aliens were killed by local forces or through friendly fire while not being revealed in shroud. I will bring it up with the team whether a captured alien should also register as a "kill" for exp and kill count as it feels like it probably should as capturing an alien is harder than killing it.

Thanks for the bug report! Yeah this was a bug I also encountered while I was prepping for a base defence mission last weekend. We've made a fix for it that will be included in the next patch which will most likely be released on stable today or tomorrow.

Thanks, we've made a fix for it that will come out with the next patch.

Replying here just to let you know that we've seen this post and very much appreciate the effort you've gone through in making it. I've brought this up with the rest of the team, we'll give this a proper read through once we get milestone 6 to stable as that's the current top priority that we're trying to sort through.

Thanks for the report! We'll look into the crash and get it fixed. As for the cyberdrone, yeah it has a pretty long range and the it deals AoE damage. It has no reaction fire though so you can take advantage of that to deal with it

Thanks for the report! There was a bug in milestone 5 that caused a crash whenever you would interact with the cheat/debug menu. We've made a fix for it but unfortunately it's only available on milestone 6.

Thanks for the report, we'll look into this. Do you have a save we can use to try to repro this?

Thanks for the report! Noticed this while I was doing another playthrough over the weekend as well, this will get fixed asap.

Sorry for the late reply, we've made a fix for this on 6.22. The bug was basically caused by the teleporter pads on the central building sharing the same IDs as the spawn pads.

Thanks for the report! I can get the effect where the speed boosts stack, but haven't been able to repro the 0 speed bug when disabling retreat/afterburners. Does this happen often or has this only happened once/rarely?

Yeah, missed this one too, thanks will look into it. EDIT: Looks like this is on the list of stuff we'll eventually fix.

Woops, looks like I missed this one. Thanks

Thanks, we'll look into it

Yeah, this is a known issue that's going to be eventually fixed iirc. Will bring it up with the rest of the team though just in case.

Yeah, we've noticed that the walls do not have their damage states linked recently but decided not to pursue fixing it as we wanted to prioritize the fixes for the various level hiding issues. We'll get this fixed once we've sorted out the more serious bugs in the game. EDIT: Nvm this is a separate issue, looks like the destruction state on this wall type got broken

Was the ground combat mission started on an older version of the game? It looks like the bug is caused by a door bugging out, which commonly happens when a save is not compatible with a newer version of the game. If this mission was started at an earlier version (prior to 6.21) then restarting the ground combat mission will prevent it from crashing.

We'll look into this, thanks for the report!

Thanks for the report! We'll look into this and get it fixed EDIT: We've made a fix for it which will come out with the next patch. EDIT2: Looks like the fix doesn't work fully, we're looking into it again

Thanks, we'll get it fixed

Will have to double check with Chris but I think these have been randomized.

Most likely just an setup issue, we'll get it fixed

Thanks for the report! We'll look into this

Thanks, we'll get it fixed

I did some testing and unfortunately was not able to reproduce the bug. Is there any chance that you're able to reproduce this on your end? If so, can you tell us what you did so I can try to copy the steps? Alternatively you can press F11 when the bug happens so the game can capture the error on the logs, then send us a bug report.

Thanks for the response! Will look into this