We've debugged the code in question manually and found that the immediate problem is that at some point in the startup some state isn't properly initialized while the game assumes it is. I modified the assembly to be more tolerant to the mistake (that is, clean up the queue that otherwise becomes irreversibly stuck for the entire game) and it fixed the issue we were having. Of course, this is only a hack - either you need to figure out why the things weren't initialized or you need to code the dependent code a lot more defensively. In our case, we found there are quite a few more places where this causes issues, most importantly (for the map we were trying to play) making it impossible for one of the players to detonate bombs. The weird thing is that I have no idea why this would be a problem for our LAN game and yet it doesn't seem to be a common problem (or at least a commonly reported problem).

Nailu

Have a nice day

Nailu and General Chaos

The problem with mining: 

I can click on tile, it changes color, but when imps come to work on it, they don't mine and start going through the selected tiles. The other player can see the walls disappear. We're playing on LAN, and both systems have both TCP and UDP unlocked for the two ports.

Gold shrine problem:

One of the players can mine, the other can not. You can claim the shrine, you can click on it, it looks active, but imps refuse to go work there and you cant mine new money (this happened on a community map, Co-op Citadel - two gold shrines right next to the hearts). This problems occurs even in single-player.

Have a nice day

Nailu