Quote from: Simon on August 22, 2026, 11:37:03 AMThe game design sets the entire stage. Execution difficulty yes or no during forward-only play? Timed bombers suggest yes, the existing control features say no.

The appropriate rewinding power follows from that and shouldn't be a standalone design decision.

Agreed, but I don't want RetroLemmini to become another replay editing machine. If anything, it's a shame that forwards framestepping was added. I accept it because even Amiga Lemmings has a pseudo 'forwards-framestep' (pressing and holding pause causes the game to repeatedly step forward one frame at a fixed rate).

Adding the ability to step backwards one frame at a time allows replays to be finely edited (thus inviting all of the UI quirks we're currently wrestling with in NLCE), and - worse - allows for levels which require framestepping shenanigans as part of their solution. RetroLemmini demands that levels can be solved in real-time, with a minimum of player-assist tweakery. I'd prefer to keep it that way.

Having said that, a way to hop backwards to a point before a mistake is a good compromise that most users do seem to want. Having said that, hrb264 has expressed that she would prefer RetroLemmini not to go down this route, and as an actual user her viewpoint is of particular importance.

I'm still 50/50 on it. And, having looked at the code briefly to see if the replay system could be leveraged to make Rewind possible, it's not trivial given the current state of the Lemmini codebase. Yes, it could be offered, but at present it would take a lot of work and the question of whether or not we should do it at all hasn't been fully resolved.

These look great! I particularly like the 'pickup vendors'

Thanks Dex. I've added this to the styles included with CE. For regular NeoLemmix, this will need to be added to the style manager.

Lix 0.10.34 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.

• Edge scroll speed is now proportional to the screen/window size. The same setting will scroll by more pixels on a bigger screen/window.
  
• Remove the tooltip that told you how to use the hold-to-sroll feature. Before, every time you edge-scrolled, Lix would tell you how to scroll with the hold-to-scroll feature, e.g., with the right mouse button.
  
• In insert mode, when you're about to replace the future of a single lix, the top of the screen tells you how many future skills you replace.
  
• When you load a replay from disk or re-watch a completed level, you don't see "Replaying. Click to play from here." at the top of the screen. Instead, the mouse curser's sidekick icon has a little letter R. Once you click, the R turns into the regular scissors cursor, the top text appears, and the next click will cut the replay.
  
• When you tweak skill assignments, the sound for a replayed assignment will now always play, and the assignment arrow will always appear. Before, they would only appear when you tweaked an assignment to a target time to which it hadn't been tweaked before. When you tweaked an assignment back and forth, sound and arrow would be missing on the second time.
  
• Re-introduce the two options whether air clicks cut the replay. One option applies when the tweaker is open, the other when it isn't open. The default is: Air clicks always cut, both with or without the tweaker.
  
• Code: The internal replay data structure now carries the lix's tribe color with every assignment in addition to the assignment's player number. This denormalizes the internal replay data structure, but it makes several parts of the program more straightforward. The networking protocol still sends plies only with player numbers to stay compatible with all Lix versions 0.10.x. The replay file format still saves the assignments only with player numbers to stay identical to the existing format.
  

<SimonN> Now the most important problem. What animal will go in the thread.
<Mindless> It's gotta be a dinosaur this time.
<SimonN> Dinosaur because Lix has turned 20.
<Flopsy> Oh dear, the Jackbox joke will have to change now. It used to be "Lix, 10 years in development and no end in sight" usually accompanied by a skeleton lying in ruins as a picture.
<SimonN> I pin the first lines of L++ to April 1, 2006. Yeah, over 20 years and no end in sight. I've been doing this for half my life now.

-- Simon

Finally got around playing through this pack! I attached my solutions. 

Some really nice puzzles here! 

Two things though:

Here and there unnecessary timers plop up and I still would suggest culling them where they are not needed! 
They mostly just trip you up without adding anything to the puzzle itself.


The most critical thing for me was this:
In one level (The knights of Ni one) hidden terrain behind the exit really bothered me! I had a solution, executed everything, the lems just needed to walk to the exit and I was suddenly 1 skill short due to the exit's frame hiding terrain! Cull a skill and remove the frame or make it properly visible!
I would highly suggest going against nostalgia here and to adjust the level.

My crusade against hidden stuff goes on and this just reminded me of my very first forum post here about a level just to find out it was hiding terrain behind hatches! This time it was the exit though. 

Sorry for the little rant. 

Thread continued from discord at the suggestion of IchoTolot:

In neolemmix, the 'owa_down' object from 'orig_fire' contains an animation error:

gif animation

The current animation is on the left, the fixed version is on the right.

This inconsistency is not present on the left/right one-way-arrows.
Only the graphics contains an error, the .nxmo file seems to already work as intended.

Attached is a graphical fix which updates the down-facing arrows to be more like the left/right arrows, as seen in the above gif.

Updates to all existing 'lemmings faithful' styles, as well as a new style, 'dex_common'.

Let me know if there are any issues! 

Hey everyone!

I'm pleased to announce a new ongoing project, dex_common.

This style was made alongside a new set of 'Lemmings Faithful' styles. Those styles are nearing completion, but I thought I'd release this one earlier, as it's a little different from all other projects that I've done so far.

It is intended to be an ongoing style of mine, which I will occasionally update with new objects, hence why I felt it necessary to make a separate forum thread.

This style isn't really a 'true' style, as it is intended to be a supplement to be used alongside another style, since it mainly contains generic objects and a few useful terrain pieces.
To clarify, each of the 'original' and 'ohno' themes from the original lemmings games use 8 unique colours for their terrain. However, for objects, they also use 6 'common' colours that are found across all styles:



The 6 'common' colours - red, yellow, green, blue, grey and white.


Included in dex_common are a bunch of objects that only use these 'common' colours.
These new objects are therefore compatible palette-wise with all the 'orig' and 'ohno' styles, as well as all existing 'lemmings faithful' styles, and are intended to be used alongside them!

Here's a little preview of some of the objects

Also included are a few generic backgrounds. I didn't feel like adding these backgrounds to any of my existing styles, since I don't think backgrounds fit with the 'faithful' theming. However, I have received requests to make backgrounds, so I felt including them here would be a good compromise. Each background uses a separate palette from all existing styles, but are limited to only 8 colours each to try and make them as 'retro' as possible. I tried to make them either as dark or as low-contrast as possible to be unobtrusive.

(Hint: use the 'background_bgdrop' object of dex_common alongside existing objects, as some objects use transparency to act as negative space.)

orig_fire's exit is a good example of an object using transparency as 'negative space'

Here's a link to the style:

https://www.dropbox.com/scl/fi/92xtqstyhm0tiureenjt4/dex_commonV1.zip?rlkey=t54ufspkhb2zkj9vvdr2gkq84&st=l7ssyzvh&dl=1

Let me know what you think, or if there are any errors! 

This is just an update to let everyone know about a minor change (see OP for details). Be sure to also check out the new button and background animation for dex_lush! (Happy belated pride, everyone! )