What's wrong with just using "X-traLems" as the title? It ain't broke, don't fix it.

Quote from: JemmingDad on October 21, 2026, 07:41:30 PMIt seems that the whole community here is well ahead of me so I'll not confuse things by sharing 'yet another remake'

All projects, particularly Lemmings-related ones, are more than welcome on the Forums. We'd love to see what you have come up with!

See this for an explanation of what MIDI essentially is, why it's different from other audio formats, and why adding support for it isn't as simple as adding the file extension to the existing list.

With that said, you're not the first person to request MIDI support in NeoLemmix and you likely won't be the last. In the linked topic, namida mentions BassMidi as a possible solution for MIDI support in NeoLemmix, and it may be time for someone (me!) to take a look and see if it can be done.

I've added it to the long-term to-do list.

Just had a quick look on Amiga Forever and can confirm that the Basher and Miner both cannot be assigned when the lemming is in direct contact with the steel. I'm not sure of the exact pixel distance, but 8px sounds about right. If the lemming is within that distance from the steel, the skill is not assigned - although we do hear the familiar 'dink' sound even in this case.

A couple of comments though:

1) This is your project, so you don't always have to be 100% faithful to the source material. I would encourage you to do whatever feels right to you as developer of this clone. It can be as unique as you like!

2) We do already have a significant number of clones based on the DOS version, and (afaik) none based on the Amiga version. I'd encourage you to use the Amiga panel graphics and general color palette rather than DOS's yucky yellow skill panel and plain black background. It would make for a good USP for your clone!

Also, welcome to the Forums!

The misalignment I'm not sure about, the green is when you have Highlight Grouped Pieces checked, as Gui said.

Please can you send me a copy of the level and I'll see if I can figure out what's going wrong.

Version 4.0 Update

A small but very significant update. Styles are now handled differently so that they are smaller and easier to maintain.

If you're using an earlier version of RetroLemmini, it's strongly recommended that you update to Version 4.0.

Here's what's new!

Style Handling

• Objects no longer need to have a separate 'om_' image with the trigger rectangle. Instead, we use maskX, maskX, maskWidth and maskHeight in the style's .ini to set the trigger rectangles.
• If you're a style creator, you can use the Editor's trigger area rendering capability (go to View > Show/Hide Triggers) to make sure you've set the correct values.
• Objects are now named 'stylename_o_n' instead of 'stylenameo_n'. This is so that styles can have names ending in 'o' without potentially causing problems.
• All included styles have been updated to this system - levels and replays are unaffected.

Force Fields

• It's no longer possible to Rotate/Flip/Invert Force Field objects. This is to keep the graphics consistent with the physics.

Entrance Hatches

• Under the new style handling system (see above), lemming spawn points are now set by the maskX and maskY values for entrance hatch objects. The spawn point is shown both in the Editor and in the updated Debug mode.
• It's no longer possible to Rotate entrance hatches (they can still be Flipped/Inverted!). If any existing levels use rotated hatches, I'm happy to add a new rotated hatch object to the 'special' style.

Up/Down One-Way_Arrows

• Upwards and Downwards-facing One-Way_Arrows have been added to all OG styles courtesy of EricDerkovits. Some of the images need to be upscaled to hi-res, which will be done over the next few weeks. You can keep the styles up to date by going to 'Help > Update Styles'.

More Java Exception Eliminations!

• When a level doesn't load, we now show exactly which resource is missing that's causing it not to load.
• The lack of a second value in the 'sound' section of a triggered object's .ini entry is now tolerated by being defaulted to 1 (so, the sound will play on the first frame of the animation unless another frame is specified) - see this topic for details.
• Improved error messages for missing resources.

Debug Mode

• Object trigger areas are now shown when in Debug mode. Please note - this should not be routinely used when playing levels as levels cannot be legitimately counted as 'solved' in Debug mode; the feature is intended for use when creating and maintaining levels and/or styles. I may consider adding this as its own feature (a 'Physics View' similar to the one in NeoLemmix), but there would have to be a lot of vocal support for this from RetroLemmini users; I'd very much prefer to keep it as a Debug-only feature.
• The panel info layout is improved and now shows object type when mousing over an object.

UI/Bugfixes

• The browser now always opens at the 'levels' folder when adding an External level.

See also - RL Editor release topic for the latest version of the dedicated RetroLemmini Level Editor.
N.B. - You must update to Editor 2.1 for cross-compatibility with RetroLemmini 4.0 - a copy of the Editor is included when downloading the RetroLemmini update to ensure that you're good to go.

---

Get the latest version of RetroLemmini here.

Version 2.1 Update

Skipped version 1.9 to go straight to 2.1 due to a significant update to Style handling.

If you're using an earlier version of RetroLemmini, you must update to Version 4.0 for Editor 2.0 to be cross-compatible.

With that established, here's what's new in the Editor!

Online Updates
 • The Editor can now check online for updates! This happens automatically once per week when starting the Editor, or can be done manually using 'Help > Check For Updates...'

Style Handling
 • In accordance with RetroLemmini 4.0, the Editor now looks to the style's .ini folder to find object trigger areas. This system replaces the 'om_' object mask images so that styles can be smaller and easier to maintain.
 • Furthermore, objects are now expected to be named with the updated suffix '_o_' rather than 'o_' as before.

Hotkey Config
 • Added 'Clear Current Key' button.
 • Bugfix - 'Edited' label persists until changes have been saved successfully.

UI / Bugfixes
 • Added default title 'Untitled' when creating a new level.
 • Rotate/Flip/Invert is now disallowed for Force Fields to keep behaviour consistent with RetroLemmini.
 • Rotate is now disallowed for Entrance Hatches (they can still be Flipped/Inverted).
 • '_pg' object gfx no longer show up in 'Terrain'.

---

Download the latest version of the RetroLemmini Editor.

Hi hrb264, thanks for taking the time to create this new style and level pack for RetroLemmini! It's great to see some creativity and personality in these levels, and you've done well to bake in a consistent theme throughout - pun very much intended!

The levels themselves are fun to play and showcase the Jewish theme well with clever titles and interesting layouts. The levels are not as easy as they look at first, and present a challenge similar to that of the "Tricky" levels in that they provide plenty of skills but also plenty of obstacles and irregular terrain to work your way around. Nice work!

As for the style, it's very inspired, very colourful, and certainly decent enough for a first effort at creating a style, which is a very difficult thing to master. I like the background color and the fact that the builder bricks are red - this is good attention to detail and really helps it to feel like its own thing.

I do have some suggestions that would improve things a bit:

You could try making all of the pieces half the size they are now. You wouldn't lose any detail at that resolution, and you'd probably find that the pieces would become a bit more versatile as well.

The objects need a fair bit of work. There are some inventive ideas for traps that fit the theme very well, but I'd definitely suggest resizing these so that they're a bit more lemming-sized and can therefore have a more appropriate trigger area. Also, the animation frames need to all be exactly the same size and offset relative to one another to keep the animation smooth and consistent. I'll happily take a look at these with you at some point - creating animated objects is no easy task!

Also, the 'metal' style is required to play a couple of the levels. You mentioned that since you're only using one piece you might add it to 'shalom' and maybe recolour it to fit your theme even more - I'd say that's definitely a good move.

Other than that, this is a very good first set of levels and style pieces. Keep up the good work!

---

I've taken the liberty of re-uploading the levels and style with the style re-named to 'shalom' instead of 'shalomx', since RetroLemmini 4.0 and Editor 2.0 can now play nicely with style names that end in 'om'. The objects also needed a tiny bit of empty space cropping off the bottom so that their height is divisible exactly by the specified number of frames - this has also been done for you. The animations themselves and positions in the level remain identical.

I'll be happy to help you develop your style further if you wish.

This is now fixed in RetroLemmini 4.0. The lack of a second value in the 'sound' section of a triggered object's .ini entry is now tolerated by being defaulted to 1 (so, the sound will play on the first frame of the animation unless another frame is specified).

Fixed in RLPlayer 4d026a2.

Quote from: lemmkeev20 on October 16, 2026, 11:11:11 AMi dont really use community edition so yeah make them downloadable styles that are compatible with all versions of neolemmix

NeoLemmix 12.14 and NeoLemmix CE use the exact same styles and always will - just thought that should be made clear.

Thanks for reporting!

Fixed in NLCEPlayer commit 8a9d103.

Quote from: UltimateLemmings on October 14, 2026, 08:55:36 AMOh no. I just discovered that the macintosh graphics also contains 1-bit graphics for the 9" Macintoshes. So guess what I naturally did...?

My guess: you've added those as low-res versions?

If so, this is even more of a reason to have these as separate "mac_" styles.

Quote from: lemmkeev20 on October 15, 2026, 12:07:47 PMi thinks we should decide which way do we make the MACINTOSH II styles be...

should they be a HR replacement OR downloadable styles

Downloadable styles, all day every day.

If they must be hi-res replacements, I'd personally want to have a lot of say as to exactly which images are selected as I'm one of the few people who exclusively uses the hi-res mode. The process of adding the images would therefore take longer, and it's likely that a good chunk of them would be vetoed in favour of other versions.

And, again, even if I was completely outvoted and everybody wanted to use only the Mac images as hi-res counterparts to the orig_ and ohno_ styles, many of the images are a slightly different shape and would need to be edited for compatibility anyway. This is not a trivial task; someone would have to do the fine-editing work for every affected piece.

Basically - if people want the Mac styles, unedited, as-is, let's just add them as their own styles and have done with it.

Thanks for reporting!

Fixed in NLCEPlayer commit 167bb84.

At present, the Lemmini codebase relies on 2 things to know the relative position and size of an object's trigger area:

1) A separate image (with an "om" suffix, which stands for "object mask") with solid pixels giving the size of the trigger area

2) "maskOffsetX" and "maskOffsetY" values in the style's .ini to specify the final position

One of these, then, is completely redundant.

The separate image can give position as well (offsets would be 0, 0) by being the same size as the object, and having the solid pixels in the exact position that the trigger should be.

Meanwhile, if we're using offset values to 'correct' the position anyway, we might as well just specify width and height whilst we're at it and get rid of the separate image altogether.

Given that the separate image inflates the size of the style on disk unnecessarily, this is what should be eliminated. We can then specify trigger area position and size in the following way:


maskX_n = x
maskY_n = y
maskWidth_n = w
maskHeight_n = h


For the above, "n" is the object's ID, whilst the values on the right of the "=" would be the correct figures required to position the trigger relative to the top left of the object, and then size it accordingly.

No need for unnecessary loading and handling of a separate image, just one easy set of values for style creators (and dev!) to maintain.

Previously, the separate image was likely useful for visualising the trigger area; this is the only reason I can think of as to why it might have initially be done this way. But now that we have visible trigger areas in the Editor, we can easily use this to ensure that trigger areas are located and scaled correctly.

So - it's very likely that the next RetroLemmini update will have this system implemented.

All styles will need to be updated accordingly - there will be no backwards-compatibility handling in either RetroLemmini or the Editor. I'll most likely create a handy tool that can output the correct values quickly and automatically, ready for dropping in to the style's .ini. Since I know of only a small handful of Lemmini style creators, and basically all styles are managed by ericderkovits and I, it's unlikely anybody else will be affected by this change.

To be absolutely clear: levels and replays will NOT be affected by the proposed update, only styles. And, they will become smaller and easier to maintain as a result!

Discussion welcome. If you have any comments or suggestions, now's the time to speak up.

Quote from: namida on August 11, 2026, 09:16:22 AMhttps://demozoo.org/productions/224224/

This seems to be what [Lemming Curd Porto Caval Shunt]'s a reference to.

And in finding this and sharing it here, I've probably instantly moved it one or two tiers up the iceberg.

That's the Paradox of something being at the bottom of a list.

For example, someone might list 'Most -> Least Interesting Songs'. The song at the bottom of the list suddenly becomes more interesting than those above it, because it automatically begs the question of why it's the least interesting, which is a point of interest!

The same thing applies to 'Most -> Least Known Facts'. Whatever is at the bottom will become more known simply by its position in the list.