QuoteC# 13, DotNet 9) and uses the MonoGame framework.

I'll have to see how to install a build toolchain for this on Linux. It should be possible; your choice of technologies is popular and MonoGame says it's available for Linux.

I'll report my results after a serious attempt to build. Happy to help you write build instructions afterward.

Quotesole exception to this [all interaction happens via skill assignments] is when the player may modify the release rate of a hatch.

Will you remove exiting during the nuke? Or did you merely not list the nuke as a second exception?

Quote"anchor pixel", is used for both terrain and gadget collisions
additional "foot pixel" that counts towards gadget checks only

It feels more natural to use only the foot (and never the ground under the foot) for both terrain and gadgets. Did you consider this? What problems will arise from this?

When you import NL levels, you'll then raise the trigger rectangle to work with the foot alone (instead of shrinking the trigger rectangle vertically to work with two separate pixels).

Quoteaiming for 99.9% compatibility

What kind of level will behave differently? Or is the 99.9% a blanket figure to allow potential future incompatibilites?

I guess: NL gadgets with 1-pixel-high trigger rectangles will not convert functionally-identically to your two-pixel collision in NeoLemmixSharp.

-- Simon

Added WillLem as board-specific moderator to: NL main, NL bugs, all subboards of NL bugs. WillLem has already been a moderator for the CE board.

-- Simon

If preservation is important: Don't move any bugs. Keep the NL bug board closed. WillLem and everybody else will file new bugs for each issue that reappears. The new bugs will be in the CE board, or in a new CE bug board. We'll link to the existing NL bug for reference.

This will filter the bugs for importance in a natural way. The urgent bugs will be re-filed. And you can always browse through the closed NL bug board for ideas.

If preservation is expendable: Reopen the NL bug board for the public. Rename it to CE bugs. Move the physics bugs out into a new board? Or close them as wontfix/as out of scope of CE?

I have no preference between these. I merely I don't like to make a big effort with lots of redirection topics.

---

If we postpone a decision here, I'll give WillLem the mod rights on Sunday anyway. Then WillLem can at least post to the closed topics, and note that they're fixed in CE. I think that's still in-line with the spirit of the closed bug board; reason:

Quote from: namidaI'm quite happy for you to have mod access on the NL ones for the purpose of reviving topics for NLCE purposes.

-- Simon

Stream is over! Recording will remain for 14 days at: https://www.twitch.tv/simonnaar

-- Simon

Yes, I think it's a good idea.

I feel namida will think that, too, but he shoud still decide this explicitly and publicly. It's his board. If namida has no other suggestions, I'll give you the mod rights in 3-4 days (on Sunday morning).

-- Simon

Ah. Similar problem then to the Fixed: Skill shadow ignores death from out-of-bounds. Yeah, the shadows don't always follow real physics.

Reworded topic title from:
New Objects interrupt skill mask in a non-interrupted instance
to:
New Objects stop miner shadow, but real miner continues

-- Simon

Next stream: Wednesday, February 26th.

I'll play more NepsterLix. Join Twitch chat or the Lix IRC (Quakenet #lix, I'll read both) and help solve!

I've added a note in my Lix that will be visible in this stream, to make it really explicit that we'll solve the puzzles together. In most other puzzle streams on the internet, you're disallowed from giving hints to puzzles. But my stream is different. It's fun to solve together!

-- Simon

Hi,

∫tan x dx develops NeoLemmixSharp, a work-in-progress C# port of NeoLemmix.

I don't have a C# toolchain readily installed, therefore I can't tell about any details. Judging only from the size of the codebase (70 % to 80 % of Lix), it looks significantly advanced. But I can't tell if NeoLemmixSharp is already playable. I assume it's not yet, because you haven't announced it yet? I'll see when I get around to install a C# toolchain here on Linux.

Last year, I've met ∫tan x dx in Leeds. You told me about this project, and that we should eventually discuss some implementation details on the forums.

-- Simon

Silken's solution to Miner Preservation Society is a backroute. I've fixed it now.

Changes to NepsterLix in Lix 0.10.30, which released today:

• Introducing Climbers: Fix typo in the title: Introdicing -> Introducing.
• Miner Preservation Society: Add some ceiling terrain. This fixes Silken's backroute from the previous post. This moves the left hatch leftward by 16 pixels (from x = 16 to x = 0) to look nicer. This broke the covering replay. I've re-covered the level.
• Cannonballs in the Air: Fix typo in title and filename: Canonballs -> Cannonballs.

---

Attached are my solutions to 5-of-all, Moon, and Planet. Many of the solutions in Moon and Planet are backroutes.

I've skipped Altruism and No Matter what I Try. These two were harder than the others in Planet. I haven't attempted Empty Walls yet. I'll continue with Empty Walls and the later ranks.

Lovely levels! My favorites: Construction Zone, Fourtissimo, Woodworms.

-- Simon

I've released Lix 0.10.30 with hotfixed DLLs. This should fix the broken Alt+Tab and Winkey. Let me know if it's fixed!

-- Simon

This is now fixed in Lix 0.10.30, which released today.

-- Simon

Lix 0.10.30 released.

Download for Windows 64-bit -- recommended
Download for Windows 32-bit -- fallback for ancient machines
Download for Linux 64-bit
Source code
Changelog
Issue tracker

How to update

Quick and dirty: Extract over your old installation. Level moves will then result in duplicate levels that remain in your level tree.

Clean method: Extract to new directory, then copy these directories from old Lix into new Lix:
user/
replays/
...and any levels that you've built yourself or added manually.

• When the mouse hovers over a gadget (hatch, goal, trap, catapult, ...), the panel explains the type of the gadget and some of its properties, e.g., in which direction and how strongly it flings the lix.
  
• Updated Allegro 5 DLLs to the hotfix version 5.2.11-nightly.20250218. This fixes the broken Alt+Tab and broken Winkey from Allegro 5.2.10 on Windows with the Direct3D backend.
  
• A replayed assignment plays its assign sound a quint lower and 2 dB quieter.
  
• Shorten the lifespan of the three flying pieces of debris after a digger has hit steel, to avoid clutter in multiplayer.
  
• Add sidekick mouse cursor. When you can click to cut the replay, a little pair of scissors appears next to the main cursor. When you can insert, a plus sign appears next to the main cursor.
  
• Fix #495: The outcome screen, after playing singleplayer level that generates the warning about huge levels, typesets the warning properly on the level's preview image. Before, the warning bled into the level name.
  
• When an internal image is missing, e.g., the mouse cursor, don't crash, but show fallback text instead of the image.
  
• When a translation string with format specifiers (%d, %s, ...) fails to conform to expectations, log the bad translation only once per program run. Before, the same bad translation could appear several times in the log file.
  

Levels:

• Add 34 new multiplayer levels by Hyperlodge.
  
• NepsterLix: Fix backroute in Miner Preservation Society. Fix typos in Introducing Climbers, Cannonballs in the Air.
  

-- Simon

Stream is over!

-- Simon

Quote from: WillLem on February 15, 2025, 11:45:23 PMassignments that fail due to an existing assignment at the same frame don't advance physics

... but all other failures to assign still advance physics: You select basher, you click on a basher, and physics advance from this failed assignment.

I agree that this combination a good choice to try in public. I'm not sure if it's absolutely best and I'd like to see feedback.

Reason: I've experimented with non-advancing failed assignment in Lix singleplayer streams. It wasn't fun to block all failed assignments from advancing physics. When an ascender/hoister is still ascending, but we know that he'll be assignable within 1-3 physics updates, I'll select builder and click on him several times. This ensures that he builds ASAP. I didn't know that I used this pattern until I removed it experimentally, and I'm putting it back in.

-- Simon

The next stream was Saturday, 2025-02-22.

More Nepsterlix. My solutions to 5-of-all, Moon, Planet.

I was happy with the UI during the stream, and released Lix 0.10.30 after the stream.

-- Simon