There's a few achievements in the game which suffer from this issue on the debrief screen. I'll pass this through as accepted it's certainly not intended. Again very minor but not ideal we'll see if there's something we can fit into the schedule to fix these.

This is one the more technically minded on our team will need to review further. It seems there is certainly an issue occuring where the game fails to load the blank scene used for constructing to levels. Which is very very odd.

Can you describe what happened before this, what were you doing in this session before this loading screen are there any similarities that come to mind to when this occurred in other sessions?

As with the other "bug" I believe this is actually working as intended. I think it is likely that you defeated Lord Saffire in the previous level and thus already own the achievement. Is this correct?

This is working as intended. If he is not defeated in an earlier level then Lord Saffire is present in Level 4 and thus the achievement can be earned here. I presume this also answers your other issue with this achievement. The same applies for Lord Coleem

I'm marking this one for further review at some point by our QA Analyst, I gave it a try but couldn't replicate either on this level or in a clean sandbox map.

Worth noting that the Sappers on this level are slightly different from the default sapper so maybe something to it. I also witnessed it on a Stream last night. 

Cian will review this at some point though it may not be until the new year. He'll be able to look into the save file as well in a bit more depth than I can.

The worst of all glitches. It exists but it may never appear again! Thanks for the report anyway. I'll bear it in mind and who knows maybe one day I'll hit the winning combination.

Ahha I see the issue now. Sorry I didn't understand from the initial report and I must have got lucky on the first time. It's based on the angle the camera zooms in at relative to the unit's position. So if you're already lined up it will appear normal.

I'll pass this through again it's very minor but well worth being aware of and we'll see if there's any chance we can fit a quick fix in. :)

We'll happily take feedback anywhere really. Direct to us on our social feeds, forums or Discord. We just don't operate a formal process around it so not liable to be pushed through as a bug ticket. 

I've been considering formalising it but we're so late on with WFTO now that it seems a little late, maybe for future projects though :)

Confirmed, can be replicated simply by increasing UI Scale when in the editor and affects every tab. Minor issue that will be put into the backlog but certainly not ideal. We'll review it in the coming months as to whether a fix will be rolled out or not.

Confirmed via the replication steps provided. Small UI flow issue, it'll be relatively low priority but we'll review it prior to 2.0 to see if we can't fix it up.

Thanks :)