There is a wormhole hex on all fights in my current shard. The hex in question is 3rd from the left, 4th from the bottom on every battlefield. Here's how it works.

My units cannot usually enter this hex (unless they are summoned into it. Probably, I haven't actually checked).

If my unit somehow ends up in this hex, they may only move to the hex in the upper left corner of the battlemat and the 2 hexes adjacent to that one.

An enemy unit CAN enter this hex. If it does, I cannot target it for as long as it remains in that hex. It can feel free to keep murdering my units if it has the capability to reach them, however. It can also attack a unit in one of the 3 hexes in the upper left corner and the target can counter attack.

I am reasonably sure that the enemy can only attack the units in the corner if one of those hexes is empty. ALSO, the unit in the wormhole hex can only move to those 3 hexes, same as any of my own units that happen to get in there. Almost had a wizard die from an enemy wormholing back into his corner.

I have not yet tested whether a unit in the upper left can initiate an attack on an enemy in the Wormhole Hex.

I am pretty sure this bug is responsible from all the game crashes I get when I use the Quick Battle option (Fn10)

It's just getting a bit silly. Anyone else ever notice this problem, or is it idiosyncratic to me?

Never seen it. Just to check, your 'wormehole' hex has normal terrain graphics and description? And I take it you're doing the campaign?

It might be helpful if you describe whereabouts in the campaign you are, if you are playing that. Which master did you last meet?

The hex looked completely normal. The terrain was proper and everything.

I was on Campaign at around shard....22...ish? I believe this was before Herskil and slightly before I decided to slap L'anshar around for his Lucky Charms.

Another Wormhole developed on the shard after that one. It was on the bottom row, 4th hex from the right edge.

I haven't seen another once for a few shards. The game had a high tendency to crash on those shards, probably because Quick Combat tried to interact with it in some way that was unfriendly?

I've only seen those 2 in my campaign, the new patch has things running a lot more smoothly on the whole.