Ah so terrain was what differentiated what turned black and didn't, I'll change the title and post to reflect that.

Thanks for the report!

Lix is on monitor A, monitor B turns off, terrain in Lix (still on monitor A) becomes black. Yeah, I should investigate together with those other monitor bugs that you filed in 2025.

-- Simon

Lix version: 0.10.31 64-bit (not the compile yourself version)
Operating System version: Windows 10 LTSC 2021 64-bit English-United Kingdom, Version 21H2 OS Build 19044.5854
Description: Recently, I was playing a two-player multi-player Lix netplay session with Simon from IRC. Whilst I was playing, I noticed one of my other monitors had a "this monitor hasn't had any activity, powering off soon, press OK to cancel"-type messages. The way I was sitting, it's a bit delicate to get up and get the TV remote to turn it off, so I decided to just let it power off, as I wasn't using it. After doing so, the terrain on Lix turned black. Also, I had two Lix windows open, I also had a second, windowed "neutrals" Lix instance, which this also applies too. I've also attached the replay to the post. After loading the next round, everything was fine agian.
Steps to reproduce:
I haven't tested if it's reproducible yet, but I suppose you should just

• Have a multi-monitor configuration
• Open Lix and load a level
• Turn one of your other monitors off
• The terrain should change black

Screenshots/Recordings:
Luckily, I like to record my Lix sessions from IRC with Simon to look back one, so I was recording this all, I will add a recording later once I figure out how to use FFMPEG to trim a recording based on two timestamps without re-encoding it, but for now, here is a screenshot.

You made a correct bet!  That's intended!

Another worry under the current 0.10 overtime rules:

Situation:
Player A has 10 points and 90 lix alive.
Player B has 20 points and 50 lix alive.
Player B cannot attack player A's bunker of 90 lix.

Problem:
Player A can now stall and B can't break this stalling.

Reason:
Player B can't nuke because player A has enough overtime to beat B with 100 points over 20 during the overtime when player B has no skills. Likewise, player B can't shepherd his 50 lix home because player A again can win with 100 points over 70 during the time when player B has no lix.

During stalling, neither player is clearly winning. B has more points, but A has more potential.

The first hunch is, again, to allow skill assignments after nuking/starting overtime. This gives B a method to break the stall: B can start overtime and attempt to kill A's lix on the path.

Or is the situation (player B cannot attack player A's bunker) too rare to bother?

-- Simon

To the users who previously raised concerns about not receiving all site emails: Has this remained the case even after the change from SendGrid to an internal service?

@Crane  I bet this is correct though 

Still a backroute unfortunately.  V3 released.  And here I thought I was doing so well with having levels that didn't need so many updates for once!

R1's are V1.
R2 is V1.

Changelog History of R3:

V2 - Small modification to the terrain at the waterline to patch a backroute from IchoTolot.

V3 - Extra entrails and blood drips underneath the platform to patch a backroute from IchoTolot.

@Crane This looks a bit more intended to me.