All right! Would you like me to put these levels in the next Lix release?

We have a few authors now who have only built one level per player count. I'll make a directory "other" for them. I'll put your 4 maps into the release here:

levels/network/2p/other/sunnydayatbeach2p.txt
levels/network/3p/other/sunnydayatbeach3p.txt
levels/network/4p/other/sunnydayatbeach4p.txt
levels/network/5p/other/sunnydayatbeach5p.txt

-- Simon

"Inside Your Router," I wasn't sure what the cyan rectangles where the arrows in the upper corners were. Doesn't matter, since the Lixes can't even get into those corners, but yea, I'm not sure what those cyan rectangles mean there.

Ah, right, you commented on those extensively in the video. Those are triggered flingers.

They're a weaker version of the flingers at the bottom middle. They have a red button and a yellow sign over it. In 2023, I put unreachable flingers into Inside Your Router purely for the decorative yellow sign. The red button is buried in the terrain below the yellow sign. Now, in 2024, we have the cyan rectangles, and the unreachable flingers became more confusing than necessary.

Indeed, describing the gadgets on mouseover will reduce the confusion by 80 %. Probably the clearest is to remove the decorative flingers entirely.

Interesting case of cultural moss, where levels from the past clash with newer game design choices.

-- Simon

I'll stream Lix singleplayer tomorrow, Saturday, June 1st, starting 17:00 UTC.

twitch.tv/simonnaar

I'm planning to play the Classy rank from geoo's pack. Or should we wait with that until geoo has time to watch, and instead play late lemforum/Hopeless, or early Nepsterlems?

As usual: Join the chat and help solve, unless you know the solution already. Apparently, this is more lenient than most other people's puzzle-solving streams. Most solvers don't want any backseating, but I'm happy to take ideas.

-- Simon

kaywhyn wrote feedback in Explain Traps/Flingers on Mouseover:

Same thing with the rewind to previous skill assignment feature, though admittedly I was negligent on the feedback on testing it before it was in stable Lix. In all honesty, I do miss the way NL implemented it, though interestingly enough namida's implementation of it for Loap is the exact same as Lix's current implementation of the feature. So, I guess I could live with this, but I'm definitely used to NL's manner of the feature's implementation, only because in this way I don't have to press the hotkey to step back a frame too.

Thanks for the feedback!

Please record a solving session in NL for me. E.g., upload unlisted to Youtube. It's hard to imagine why you want to rewind to exactly 2 physics updates before you see the assignment, not to 1, or 3, or 4, or ... Skill assignments aren't that often late by exactly 1 physics update; they're late or early by a few. I'd like to see your NL usage in the general case.

You rely on a bug in NL, or, more specifically, on a leftover workaround for a fixed NL bug. There can be value here. It's always possible that accidental features end up more useful than what we design. But I'd really like to see it in action first before I implement anything different than the obvious rewind to the physics update immediately before the assignment.

To pull assignments earlier/later by 1 physics update, try the replay tweaker. You'll get your result faster than with any NL workflow.

-- Simon

Dish of the day, serves 4 people:

• 600 g noodles
  
• 1 celery (= Stangensellerie, not Celeriac = Knollensellerie)
  
• 2 onions
  
• 700 g minced pork (probably works with minced beef, too)
  
• 600 g crème fraîche
  
• 500 g spinach, deep-frozen creamed spinach
  
• 400 g lentils (drained net weight is 260 g)
  

It's a variant of one of my classic pasta sauces; the classic sauce is minced meat with cream and spinach. The upgrade here is the celery. It's knackig! It's curly!

Start by preparing the classic sauce. Fry onions with the minced meat. When both are well-done, extinguish them with the cream. Add spinach. Add lentils. Let this cook for as long as it likes. Stir occasionally. Rule of thumb with every pasta sauce: The sauce shall wait for the pasta, not the other way around.

Cut the celery into small curly pieces. Insert them into the sauce when you like: Either early, which makes them blend in well, or later, which keeps them knackig, but they'll run the entire show themselves. The bush (= the leaves of the celery) tastes well, cut it and put it in, too. Toss away only the wooden parts near the bottom.

---

After dinner, we played 2-color Igel Ärgern, see image: back of box. Then we played 6-color Igel Ärgern with:

• Both players run 3 colors each. You win as soon as one of your colors wins, i.e., as soon as you have 3 out of 4 same-colored hedgehogs in the goal.
  
• We added the doping rule: First hedgehog to reach the goal gets disqualified for blatant doping. Its color can still win if all 3 remaining hedgehogs reach the goal.
  

At first, with 24 hedgehogs in the running, this seemed to take ages, but it produced a close endgame with hard decisions.



Then we played Sneak heads-up, but we added geoo's beer-and-pretzels rule of Kontra. When you challenge a sneak, you may announce Kontra to make all revealed cards score 2 points instead of 1 point. Against a Kontra, the sneaker may reveal as usual, or he may fold to lose his cards unrevealed.

-- Simon

Sounds great. I'll happily try the Lazarus build. Crane, let me know when you have something to test.

The GR32 port wouldn't be urgent for me. Everything here runs on x86_64.

-- Simon

I can't run V12.13.0 RC both on my pc and laptop.
This is the error message I got:

Idea: There are at least two new images in the RC1:

./gfx/panel/nolems_message.png
./gfx/panel-hr/nolems_message.png

Do these exist in your NL tree? Or did you take the executable from the download and nothing else?

Even if you installed the entire RC1: Maybe NL calls into outdated graphic libraries on your system. I don't know if it's possible with PNG to run into new compression formats, but, as a wild guess: Open the images in a graphic-editing program of your choice, then re-save them as PNG. Does that make NL happy?

(It would spoil the wild goose chase if the message told you which image it tried to load. On the other hand, it doesn't seem to be entirely NL's fault; grepping the source for variations of "Unknown image format" finds nothing. Looks like it comes from within one of NL's libraries.)

-- Simon

In 0.10.23, chat lines will be colored according to player colors.

I haven't touched the line wrapping behavior for 0.10.23. Only the first display to receive chat wraps correctly. After you return from play to lobby, the lobby will obtain the chat lines (which the game's chat display has wrapped) and chop long lines, which is the bug.

-- Simon