There is an option to disable automatic naming. Should you use this option, a Save dialog will pop up every time you save a replay, allowing you to completely choose your own filename.

I know, but usually when playing through a level pack, I want to save just one replay. So it's more convenient to use the automatic names first (and perhaps later rename them). But when I then come to a level with alternative solutions, I cannot change the option at the results screen any more. 

Recent game mechanics changes made the attached solution/backroute to "Won't get fooled again" (again) possible.

And here is a new version already.

Goal of this change: Make the level bigger to have more space to play around.

Main change: I just mirrored the level.

Secondary changes (feel free to do whatever you like with these):
- 20 lemmings instead of 10 lemmings, because the number of hatches doubled as well. RR set to 50, because RR 1 is sooo slow.
- Removed some of the steel, that I thought ugly and saw no use for.
- Removed two unlock buttoms and kept only the necessary ones.
- Moved a few parts (e.g. the hatch) one or two pixels to have them properly centered.

General remarks:
- Even though the level is currently symmetric, it does not need to stay this way.
- The level still allows for lots of solutions, inculding one that still uses only one of the bashers and miners. The attached solution uses more skills however.

OK, let me try to be clearer:

Why should cloner skills be included in the lemming count?
Because currently the preview screen does give the player a wrong impression! Let us consider two examples:
1) The example you mentioned: 50 lemmings out of the hatch, 5 cloners and a save requirement of 45 lemmings. Given the current info on the preview screen I expect that only 5 lemmings may die. But in fact even 10 lemmings may die, so once the level starts I need to adjust my count due to the existence of cloners - precisely the thing you wanted to avoid.
All this stays true, if the same solution would work with 55 lemmings in the hatch and no cloner (i.e. the case, where one does not need the cloners in the solution). And it stays true as well, if all five cloned lemmings are among the 10 lemmings that need to die. 
2) Consider the attached level: 5 lemmings coming out of the hatch, 5 cloners available and a save requirement of 10 lemmings. Then on the preview screen I have three options, what is displayed:
- Percentage ADJ: I have 5 lemmings and need 100% --> Misleading information.
- Percentage ON: I have 5 lemmings and need 200% --> How can I save more lemmings than I start with? Confusing.
- Percentage OFF: I have 5 lemmings and need to save 10 lemmings --> How can I save more lemmings than I start with? Confusing.
The point is: I do not start with 5 lemmings, but with 10 lemmings. Out of these 10 lemmings I can create 5 lemmings using the cloner skills whenever I want. But this does not change the fact, that I have 10 lemmings available. Again the current info on the preview screen does not allow me to compute the number of lemmings that may be killed, and is therefore misleading.
Summary: For the player to get the correct expectations, one needs to add the lemmings in the hatch, the preplaced lemmings and the cloner skills to get the correct number of available lemmings to display on the preview screen.

This is kind of the same argument as for the zombies you mentioned, but in the other direction: zombies/ghosts are currently counted as lemmings, though they are not available to the player - cloners are not counted, though they create lemmings that are available. Neither thing is good.

What do I mean by "forcing to use cloners"?
Consider now my replay: Using only one cloner, I created a save path from the hatch to the exit. So the level looks pretty much solved. However due to the save requirement of 10 lemmings, this is not the case! This level forces me to use the other 4 cloners as well.
Sure, if the save requirement would only be 6 lemmings, then I might omit assigning the other 4 cloners. But level designers usually expect one to use all cloners (because they use them in their own solution), so this happens only rarely.

If the level requires that I use a cloner already in the middle of the level, then everything is fine, regardless whether the cloned lemming dies or not. In this case none of the suggestions makes any difference, because the cloner skill is no longer available at the end of the level.

What is the idea behind my most recent suggestion?
Well, it should probably revised to
  If the last lemming exits, the save requirement is not yet reached and there are still cloners available, then one of them should be assigned on the last frame.
The point is: Under these circumstances, the player very likely does not want to end the level (because it is not yet solved), but wants to try to save some more of the cloned lemmings. So the aim of my suggestion is to avoid going to the result screen (with the failure), but to continue the game to give the player a second chance to save the (not yet created) cloned lemmings as well. The intention is basically the same as with Simon's " level must not terminate" suggestion.
As an example, let us again consider the attached replay. After the first cloned lemming and the first 4 lemmings from the hatch have reached the exit, there is only one lemming left, but still 4 cloner skills. As 5 more lemmings need to be saved, it is very likely a stupid mistake from the player (me) not to have the other cloner skills assigned earlier. So I should have assigned the cloner already at sometimes earlier and the game only tries to correct my mistake at the lastest possible moment.
This does not "take away control from the player", because it only changes things at the very last possible moment, but rather gives the player more control, because the player is given another chance to save lemmings. It does "make the game easier" only in the respect, that it catches one possible and obvious mistake a player may make, but doesn't do anything the player cannot do himself.
Finally, you question the benefits: If the newly created cloned lemming arrives at the exit without any further guidance (which is not automatic as you already noted), then this helps the player solving the level. If the cloned lemming cannot be saved, then this at least alerts the player that he needs to save a few more lemmings and therefore can either go backwards in time or start the replay from the very beginning. In any way, this is a better outcome than going to the results screen.

No, it is terrible. I have compared it to making all exits invisible during play, showing them only during preview.

...and people came and even created levels with hidden/invisible exits .

The idea hinges on the current problem that (leaving results screen by any means kills your replay). Fixing that is more important than special-casing the termination of LemGame.

Totally agree with this.
And thanks for the clarifications. I still see problems with them, but perhaps it is best to hear first namida's thoughts on adding "go directly from results screen to replaying the level".

After thinking some more: My combined idea of 1) add cloners, 2) don't score cloners, is idiotic. We'd end up with a level void of lemmings, but displaying lems left equal to cloner skill count left. This idea implies they should be scored automatically. Or not be counted with the out count. Whargh.

Or perhaps this discrepancy can be explained by a message in the results screen like "Perhaps assign all cloners next time? Hit hotkey XYZ to replay your solution."

Edit Simon: This topic belongs to a series of related ones:

• Save requirement: show during play
• Required-saved, out+hatch: display during game
• Add cloners to initial count of lems (this one)

---

Two questions, because I just played a cloner level:

1) If we display "required - saved / out + hatch" how do we count cloner skills? My intuition says: "required - saved / out + hatch + cloners".

2) Assume that at the end of the level when all lemmings are either saved or dead, a player has a few cloner skills left. Should these be automatically added to the saved count?
Pro: If I don't need cloners, I tend to forget to assign them while playing. More than once this resulted in me failing a level only due to this. I found this quite annoying.
Contra: Currently one may create levls, where the main problem is turning around cloned lemmings.

I realize apparently no one else considers this a problem but I do: I wish for a volume control of some kind because I think the default volume of both sound and music is way too high.

You are certainly not the only one who consideres this a problem. But it is already on the list of changes for NeoLemmix V2.

PS: Perhaps the current discussion should be moved to a thread in the NeoLemmix V2 subboard, because it mainly belongs there?

Not sure I totally agree with Simon's list. The most important stats are in my opinion:

• allowed kills left: Yes, useful and important for many levels.
• required - saved: In levels with many lemmings and low save requirements, this would be helpful. Seeing "2 more required" seems more helpful than "78 allowed kills left".
• hatch: There are a few levels, where the nth last lemming (for very small n) needs a skill assignment very soon after appearing or a release rate change is required then. Then this value helps a lot here.
• required or allowed kills initially (or something mathematically equivalent): Assume you realize in the middle of the level, that your solution does not quite work. Then having these two values available helps in determining fixes. But as the above would already display them at the beginning on the level, perhaps only display them ALTernatively after pressing some key.

Further comments and comparisons with Simon's list:

• required - saved: This is mathematically equivalent to Simon's out+hatch if allowed kills left is displayed, but seems easier to work with. I actually don't know what useful information out+hatch gives, but even if so, then adding the two values is easier than substracting them. Note as well, that at the start of the level required-saved plus allowed kills left gives initial.
• required: This is a fixed value that doesn't change. So it is of little value as a constant reminder. Of course, one may display both required and saved instead just their difference.
• died: Why would I want to know this? It just allows to compute certain more important values, so better display these.

So my proposal is to display just two values: required - saved / out + hatch
This pair makes sense as an answer to "How many of the still available lemmings do I need to save?" and allows an intuitive approach to allowed kills left. If there is still space left, one might display "hatch / initial" as well.

PS: Is it actually useful to display "TIME ----" all the time, even when the level has no time limit at all? Perhaps for levels without time limit, additional info can be displayed instead of "TIME ----".

Two only tangentially related questions:
1) What is the cheatcode for GigaLems? I remember some good levels in there, but don't want to play through the whole pack again.
2) Where can I find Resident GigaLems? This thread ends with an announcement "All levels are created", and this thread ends with an extension of the test period, which is long over by now. But neither seems to contain a link to the actual level pack.

And one suggestion for the actual voting: Would it be possible to link to pictures of the various levels, similar to what was done in the "Best level in Orig/OhNo/... lemmings" vote-offs?

PS: namida's list of my levels seems to be essentially complete, though I wouldn't term the levels namida linked to as released. These were added as examples how the one-way-arrows can be used currently, and not to be played and solved.