I've said my input that the magenta is a bit eye searing at point were I have to turn it off when im making the levels. I'm standing on these choices for what i'd suggest.

Basic RGB value - default it to the original color, change it by sliding the values to something more easy on the eyes, include presets via a dropdown menu if you're worried about those spending time in the options

A softer contrasting color - While colors like magenta and yellow are contrasting, finding a contrasting color that's visible enough without it being blindingly bright would be a better solution, colors like Purple or Light Teal (think the color of baja blast) may be more easy on the eyes

It's been a long while since we've played due to myself taking a step back from arranging the sessions during my house buying process. I'm now settled in and with the summer starting to wind down, it's probably a good time to start playing again. Thanks to Silken Healer for stepping in to arrange a session during my absence 

Anyway, Simon and I have arrived at a date of Sunday Sept 14th at 5pm UTC (6pm UK time).

Same as usual, we usually voice chat on Mumble client which is free to download. PM Simon for the Lix server info.

Also try to make sure Lix is as up to date as possible as well to help Simon with bug reporting (0.10.31 at the time of writing)

It seems that the easiest and best solution to this is simply to add the erasers to the styles collection as "erasers". Then, like "default", they can be a standard set that is supplied along with NLCE.

The benefit of this is that anyone can add pieces to it as they wish, so it can be collaborative and as-needed.

Pieces would of course need to be agreed upon before they are added to the set. If existing erasers can reasonably be used to create the desired shape, there shouldn't be any need to add more and more pieces exponentially.

Thoughts?

Currently unsure what to do about this. This one feels like it might get into "too many options" territory; I agree with Simon that this is a design choice that should be solved program-side. We don't want users spending too much time in the options menu.

Then again, it would be easy enough to add the option, and I imagine that for most people it would be a set-and-forget kind of thing. Maybe a choice of 3 options, whether it be different colours or different brightness/opacity, would suffice for this one?

Input needed. As it stands, nothing will change.

Quote from: WillLem on July 08, 2025, 02:38:13 AMOutline wouldn't be the best idea for water and/or OWWs because in both cases the trigger area affects whatever it overlaps, including any added terrain:

This is true for almost all trigger areas - and ironically, at least on the player side of things, OWWs are actually one of the few exceptions. In DOS/Lemmix it's indeed the case that they affect anything they overlap, but in NL (and presumably SLX by extension), when the physics map is generated at the start of gameplay, OWW data is baked into it at that point. If a pixel is erased (by an eraser piece, or during gameplay, by a destructive skill), the OWW flag is erased with it; if a new solid pixel is later placed in that same location, it's just a normal pixel with no OWW flag. If the pixel wasn't solid at the time of generating the physics map, it didn't get the OWW flag in the first place.

(And by extension, yes, this does mean that SLX could theoretically add a constructive skill that creates one-way walls, with no changes to any wider object / terrain physics. Whether it's a good idea is a very different question, but it's very possible on a technical level.)

Quote from: WillLem on August 01, 2025, 12:05:16 AM@namida - Is there a reason why the trigger areas are all that very specific shade of pink (#F000F0)? I've noticed that Lemmini uses a very similar shade (#FF00FF), and that DOS variants of Amiga colours follow the pattern indicated by these colours (so, for instance, #4422FF in Amiga would become #4020F0 in DOS, and vice versa). I wonder, then, if the choice of shade for trigger areas is simply what was used in the base game that each clone was based on (so, #F000F0 for Lemmix's DOS base and #FF00FF for Lemmini's WinLemm/Amiga base).

It's very likely I chose to intentionally go with a color that's within DOS's color depth, hence #F000F0 instead of #FF00FF. The choice of using "death magenta" in the first place is simply because it tends to contrast well with a lot of other colors, and in particular, it itself tends to be a less-frequently-used color in actual graphics (as opposed to UI). It's a pretty common choice in general for this sort of purpose, not just Lemmings-specific.

Ah, I had only found namida's [BUG] PM attachments sometimes failing to send, but not your investigation in the 2.1 update topic.

You've already reduced this to the double/triple previewing. Good work.

Yeah, the checkmark UI is strange in the first place (instead of, e.g., pushbutton to delete one attachment), it's bugged, and it's unresolved a year later.

-- Simon

Yes, I've noticed and posted about this problem in the SMF 2.1 Upgrade topic, in these two posts:

https://www.lemmingsforums.net/index.php?topic=6856.msg105291#msg105291

and

https://www.lemmingsforums.net/index.php?topic=6856.msg105886#msg105886.

This I've observed ever since the Forums software upgrade took place. It's still a problem a year later.

namida apparently also made a topic on it too:

https://www.lemmingsforums.net/index.php?topic=7122.0

• Start composing a private message to another forumer here.
  
• Attach a file: Click Browse, pick a file from disk, and wait for it to have uploaded successfully.
  
• Click Preview.
  
• Click Preview a second time.
  
• Click Preview a third time.

Expected: The attachment is still ready to be sent. It should be listed below the composed message text, and its checkbox (where you pick which attachments you want to send) should be checked.

Observed instead: The attachment is gone.

• In the first preview (= after step 3), it's ready to be sent, as expected.
  
• In the second preview (= after step 4), it's still listed, but its checkbox is off. This unchecking is the bug, because we won't send an unchecked attachment.
  
• In the third preview, the attachment isn't even listed anymore under the text. And again we won't send the attachment now. This is technically correct because step 4 unchecked the attachment.

Now I had to send a second PM and look like a dunce who announces attachments and then fails to attach them. :-P I compose bottom up: Attach first, then type the text, then type the subject line, then add the recipients. It's near-impossible to forget it this way, and I investigated and found this repro. Happy Simon.

-- Simon

Despite asking several times, no one has had anything to say about the new setup (outside of the one-off aforementioned case with the post being flagged for mod review). I'm going to go with the "no news is good news" assumption here, but if this is wrong - please actually reach out to me if it's causing problems. Don't assume that someone else will be having the same issue and report it for you - this community is far too small for that assumption to be reliable. And just in case anyone got the wrong idea, we are definitely not going to warn you or ban you or tell you off for reporting a technical issue. If for any reason you don't feel comfortable discussing it with me, you're welcome to raise it with a different staff member instead and they can pass it on (anonymously if you wish, although anonymity may limit how easily I can investigate).

I can also say that:
- Either no spambots have slipped through, or mods have been very quick at cleaning them up. (I also assume that if such had happened, it would've gotten back to me.)
- Aside from the one case mentioned above, no genuine posts have been incorrectly flagged for review or outright blocked.
- I have noticed a sharp decline in the number of guests viewing the site since setting up CleanTalk. This is expected - where it suspects a particularly high risk of spam, it blocks the site altogether rather than just preventing posting / registering. (This should also help with the database crash issue - I still haven't figured out exactly what leads to it and we're still relying on the "temporary" fix of having a background script that checks and restarts it periodically if needed, but it appears to be the database getting "overloaded", which is far less likely if we're not getting slammed with page loads from spambots.)

Quote from: WillLem on August 21, 2025, 11:39:00 PMThanks GigaLem. I'm afk at the moment (on mobile) but I'll take a look at these at some point for sure.

Namida, what did you mean about generating these images automatically? Would this be instead of creating the style, or as a way of quickly adding new pieces to it? Or as something in the Editor that can create them on-the-fly?

I was simply thinking of it as a way to generate the images.

A built-in feature in the editor sounds useful on the surface, but I'm actually a bit hesitant to recommend it. It would really need to be supported in the player as well as an actual feature rather than just a piece-creation tool in the editor (otherwise, you're going to end up with a bunch of user-generated erasers that not everyone is guaranteed to have, and a huge mess trying to keep them in the styles collection up-to-date), but then that would break 12.14 compatibility. It could be a useful idea for SLX.