NeoLemmix V12.14.0-RC Released

[namida]

The release candidate build for V12.14.0 is here. V12.4.0 may very well end up as the final version of NeoLemmix, so make sure to report any newly-introduced bugs (whether introduced in these RC builds, or in V12.13.0.)

Currently, I do not expect to move 12.14.0 to stable at least until bug reports for NL close altogether.

If you are looking for the stable version of NeoLemmix, you're after 12.13.0: https://www.lemmingsforums.net/index.php?topic=6835.0

Known issues

Currently none

Changelog, V12.13.0 -> V12.14.0-RC1

- Fixed bug: Fencers turning around at steel is inconsistent depending on the exact position of assignment.
- Fixed bug: Shimmiers can in some situations shimmy along the bottom of the level.
- Fixed bug: Shimmiers can be assigned to sliders who are leaving the bottom of the level.

Download (V12.14.0-RC1): https://www.neolemmix.com/download.php?id=598
Note that unlike usual for RC builds, the editor is NOT included. This is because there are no changes needed to the editor for this update; so use the stable version of the editor instead.

This download only includes the Orig and OhNo styles, plus "default", "xmas" and "special". You can use the in-game Style Manager (in the Settings) to download other styles, or you can download styles manually:
- All styles: https://www.neolemmix.com/download.php?program=52
- Any individual style: https://www.neolemmix.com/styles/12.11/XXXXXXXX.zip (replace XXXXXXXX with the style's name, eg: https://www.neolemmix.com/styles/12.11/orig_fire.zip for orig_fire - and no, "12.11" in the link is not a typo)

What is a Release Candidate build in the context of NeoLemmix?

A release candidate build could be thought of as a pre-release version of an upcoming release. The idea is that except for bugfixes, or issues that were specifically noted as "should be tested during the RC phase before deciding", there won't be changes between it and the stable version, and thus it can be used to start updating content, as well as for ironing out last-minute bugs. Content specifically targetting it should not be released, though styles targetting it can be submitted for the next styles download.

What do I need to do with my existing content?

12.14 consists purely of bugfixes; it will not introduce any new features. However, as it includes physics bug fixes, make sure to run a mass replay check on your levels - especially those using the Shimmier or Fencer.

[Strato Incendus]

Okay, I didn't expect that one bug report of mine about the Fencer hitting steel to result in a new NeoLemmix version. 
I thought we'd simply have to live with the pixel precision of the assignment here (much like assigning a Builder or Miner can result in the lemming turning around or not, depending on a difference of just a few pixels).

I appreciate your commitment to solving this now, and even shifting what I thought would be the final version of NeoLemmix (12.13) to one version later (12.14).

The Fencer and Shimmier however both feature heavily in my packs - the Fencer changes may even affect Lemmings World Tour - so the mass replay checks may uncover quite a few side effects.

I was planning to release Lemmings Hall of Fame for 12.13 today, but I don't think this makes any sense now, if 12.14 is on the horizon.

[IchoTolot]

Just done a quick replay check for my stuff and I found 3 cases of replays that needed fixing for this RC.

All 3 times it was the case of "fencer hitting a steel wall right in front".

The levels were:

NL Intro Pack: Advanced training 3 and 5.
Lemming United: Neutrality 16.

So "Fencers turning around at steel is inconsistent depending on the exact position of assignment." should be the biggest cause for replay adjustments from my first round of testing. 

Edit: Attached the old "broken" replays for reference.

[namida]

Okay, I didn't expect that one bug report of mine about the Fencer hitting steel to result in a new NeoLemmix version. 
I thought we'd simply have to live with the pixel precision of the assignment here (much like assigning a Builder or Miner can result in the lemming turning around or not, depending on a difference of just a few pixels).

I appreciate your commitment to solving this now, and even shifting what I thought would be the final version of NeoLemmix (12.13) to one version later (12.14).

The Fencer and Shimmier however both feature heavily in my packs - the Fencer changes may even affect Lemmings World Tour - so the mass replay checks may uncover quite a few side effects.

I was planning to release Lemmings Hall of Fame for 12.13 today, but I don't think this makes any sense now, if 12.14 is on the horizon.

I did say "there might be a couple more small bugfix updates" .

It's simply a new major version (12.14.0 rather than 12.13.1) due to the fact it introduces physics changes. If it was just a couple of UI bugfixes, it would've simply become 12.13.1.

FWIW, I don't think the Slider / Shimmier changes will cause any issues. If they do, the issues are almost certianly bugs, not intended changes, as the changes to those skills relate specifically to situations that it's glitchy for them to even be in in the first place. The Fencer-steel situation is the big one to keep an eye on here, firstly because it can cause a different outcome in normal situations, and secondly because the Fencer code is a bit of a hot mess and even with this change being quite simple (just a difference in which situation takes priority, after the situations have been checked), side effects are not out of the question.

[kaywhyn]

Ran a MRC on mostly level packs that use the fencer skill but also a few that use the shimmier and these were my results:

Stratos' packs:

Lemmings World Tour - No breakage

Lemmings Open Air - No breakage

Lemmings Hall of Fame (this pack of Strato's is still in private pre-testing with me) - No breakage

Nessy's Pack

Lemmings Destination - No breakage


Armani's Pack

Halloween Lemmings 2023 - No breakage

Ichos' Packs

Lemmings United - No breakage, so my Neutrality 16 replay from several years ago still passes

NL Intro Pack - 1 breakage, Advanced Training 5 just like Icho due to the fencer/steel interaction. Pre 12.14RC the fencer didn't hit the steel and therefore didn't play the clink sound in my replay. Now it does with it fixed in 12.14RC and hence threw off all skill assignments in the replay after hitting steel.

namidas' Packs

Lemmings Plus Omega 2 - No breakage

Lemmings Plus VI - No breakage

Lemmings Plus Alpha - No breakage

tan x's and Dexter's Pack

Renaissance Lemmings - No breakage

GigaLems' Packs

FM 2018 - No breakage

FM 2019 - 1 breakage, Binghe 4 which isn't due to the fencer/steel interaction but instead the fencer hitting down OWAs, which is essentially the same as fencer hitting steel because the fencer hit OWAs going in the wrong direction.

FM 2020 - No breakage

FM 2021 - 2 breakages, Ox 4 and Dragon 5, but as these are slider levels, these are slider-related issues, not fencer, meaning the 12.12.5 replays I have for the pack would first break in 12.13 instead. There are fencer levels in this pack too, but they all check out fine according to the MRC

FM 2022 - No breakage

FM 2023 - No breakage

Freedom Planet 2 Sampler Pack - No breakage

edit: Attached my Binghe 4 replay

[Strato Incendus]

Thanks for the info, namida!

Also, thanks to kaywhyn for having already mass-checked your replays for my three major packs. This confirms they levels are all at least still solvable.
Of course, only I have replays for all the intended solutions, so I still have to check if any of those broke.

[namida]

FM 2019 - 1 breakage, Binghe 4 which isn't due to the fencer/steel interaction but instead the fencer hitting down OWAs, which is essentially the same as fencer hitting steel because the fencer hit OWAs going in the wrong direction.

Although it's been referred to as "fencer/steel", both the bug and the fix apply to wrong-way OWWs too.

[kaywhyn]

Also, thanks to kaywhyn for having already mass-checked your replays for my three major packs. This confirms they levels are all at least still solvable.

Np!

Of course, only I have replays for all the intended solutions, so I still have to check if any of those broke.

Yes, the MRC results might very well be different for your set of replays of intended solutions and hence might uncover some breakages somewhere. I have confirmed that all of mine still work for your packs

FM 2019 - 1 breakage, Binghe 4 which isn't due to the fencer/steel interaction but instead the fencer hitting down OWAs, which is essentially the same as fencer hitting steel because the fencer hit OWAs going in the wrong direction.

Although it's been referred to as "fencer/steel", both the bug and the fix apply to wrong-way OWWs too.

Right, OWAs going in the wrong direction for the destructive digging skill acts like steel

[namida]

Right, OWAs going in the wrong direction for the destructive digging skill acts like steel

Yup - and most code (including the Fencer code) runs through a combined "check for indestructible terrain" function. This function takes the skill being used as a parameter, from which it figures out which directions of OWW to check and which to ignore. Steel only gets specifically checked for when determining whether or not to play the "clink" sound (I think there could be very specific edge cases that would trigger the turnaround on steel but would fail to play the sound, not just for the Fencer but for the Basher too, but this isn't a big enough deal for me to worry about at this point).

[WillLem]

The cursor-during-zoom bug originally reported by Simon has now been fixed. The behaviour is now at least on par with Lix's zoom, so should be acceptable.

Here's the fix if you want it, it's a very minimal change so rather than PR I've just pasted the code into the linked reply. Note that it might need some testing for stability, and further improvements may be possible, so it's probably worth including in the next 12.14 RC (that is, if you do wish to go ahead with it).

[namida]

Last call for reporting any issues that exist with this RC build. As a reminder, general bug reports for NL are now closed, so only issues that are new in this RC (but don't exist in the stable version) should be reported at this stage.

If an issue comes up a week after release that would easily have been caught during RC if people had made a basic effort to do so (eg. something that becomes clearly apparent the first time someone mass replay checks their pack), I will NOT be making a further update to fix it.

If nothing comes up, I will do the stable release in a few days.