So - since this is likely gonna be the last V1.xx update (not that I haven't said that before, but bugs keep showing up T_T), I'd like to get some public testing before officially releasing it.

Give this a go, and let me know if you find any new bugs, or major bugs that I've overlooked.

https://www.dropbox.com/sh/ewioeyogkxlegig/AACIvxzfMXo72Gnrx9Al8OiRa

That folder contains the release candidate versions of the Flexi Toolkit and NeoCustLemmix. Since I realise not everyone who might otherwise be willing to test would want to make their own content, I also included copies of Lemmings Plus III and Lemmings Plus Omega.

There's a "NeoLemmixHotkeys.ini" file in there. This one is configured with a setup similar to the Lix defaults. If you want to use the NeoLemmix defaults, just run the player without any NeoLemmixHotkeys.ini file and it will automatically generate one using the NeoLemmix defaults.

Please keep in mind that this is a TEST VERSION and while it's fine to release packs based on it, please be prepared to update them to the final release if there are any changes - this should simply involve rebuilding the EXE with the Flexi Toolkit, and shouldn't need any changes to any content.

V1.36n
------
* Added support for customizable hotkeys. These are saved in the NeoLemmixHotkeys.ini file, where
  they can be edited by hand if desired, or copied to other folders. (Multiple players in the *same*
  folder will indeed share this INI file.) To configure them, enter the Config menu (F3 on the title
  screen) then press T.
* Added two new default hotkeys; < is backwards frameskip 5 seconds, and > is forwards frameskip
  5 seconds.
* A missing music file no longer causes the game to crash.
* A text file is no longer saved alongside the replay by default. It can still be saved if automatic
  replay naming is turned off, by choosing "Replay + Text File" from the format dropdown box in the
  save replay dialog.
* Fixed the following bugs:
  > Lemmings that fall into a digger pit being dug by a ghost often get stuck in terrain
  > Two-way teleporters sometimes cause the complete disappearance of lemmings
  > Whether or not a climber splats from a fall can be affected by the position they start from
  > Multiple skills can be assigned in a single frame via various methods, often breaking replays
  > If a lemming is highlit while paused, the change is not immediately visible
  > Finding secret level triggers also unlocks the next non-secret level
  > A L1 sliding glitch-like setup allows gaining a small bit of extra height

This topic is for entrants to post updates to their levels only. Any posts in this topic, other than for the purpose of entrants posting updates to their levels, will be deleted. If you are simply wanting to discuss the levels, please use this topic instead.

Please follow these rules when submitting updates:

1. Please don't leave multiple versions of your levels in this topic. When posting a new update, remove the attachment from the old post.
2. Don't edit your old post to attach the new update, even if there have been no other updates since. Make a new post for a new update.
3. Any posts that have had the attachments removed (due to being superceeded by a new update), I'll delete eventually. (Any other mod/admin is also free to do this.) So don't leave any important details in them (or if you must do so, copy the details into the newer post).

These won't be enforced as strictly as the "official" rules of the contests; but I do still ask that you follow them to keep things simple for me updating the entries, as well as others trying to find the latest updates.

Well, the votes are in, the polls are closed, and we have our winners!

1st Place
GigaLem's "The bURns of DrEAD"
Prize: (Not yet chosen)

2nd Place
IchoTolot's "Lemmings in Unison"
Prize: Choice of rules for next contest

Congratulations to our winners! As usual, new contest will be up when the rules have been chosen, if someone chooses to select them as their prize; or otherwise, sometime in the next few days.

So - the basic reason for the "NeoLemmix" name is that NeoLemmix - or at least, NeoLemmix V1.xxn branch - is a fork of EricLang's Lemmix engine; similar to how SuperLemmini is a fork of Lemmini.

When I decided to do the reboot, I originally decided the name "NeoLemmix" should be kept, despite that the reboot would have little - if any - Lemmix code still in it, on the grounds of that it's still continuing to implement NeoLemmix's mechanics, feel, etc. But with more and more decisions that go away from NeoLemmix 1's structure, it's starting to have little resemblance towards NX1 apart from being a lemmings engine with the same additional skills and object types. Essentially, rather than being a new version, it's starting to feel more like, at most, a spiritual successor.

So I'm wondering - should the name be changed from "NeoLemmix" to something else? And if so, what should that something else be? I would like to keep a name that in some way evokes this connection to NeoLemmix (V1.xxn branch); since keeping "Lemmix" in the title is a bit inappropriate, perhaps something that still includes "Neo" in the title?

It's pretty clear that - no matter how sure I am that a proper binary format is preferable to NeoLemmix's design - some people are never going to give up on insisting that their way, and only their way, is supported. As much as I'd rather do it the way I prefer, and the way that I see working best for NX2 - more than this, I would rather avoid a situation where development stalls forever (or worse, I decide I've had enough of the arguments and cancel the project) over debate regarding how to use graphic sets. So - fine, directory structure it is. And no, no other formats will be supported, except semi-automated conversion (not direct use) of legacy formats.

Now that that's out of the way, let's try and at least have a reasonable discussion on how they'll be implemented, and what features should be supported. Also - how exactly, under such a framework (since I think if we're going to go for this structure, we may as well abandon any notion of a "graphic set" beyond as a way to categorize pieces into seperate sub-folders), should features that are usually tied to the graphic set - such as brick color, one-way arrow graphics, etc be handled? Should they be specified on a per-level basis, or should there be "header" type files which contain different combinations of these? Etc.

I've mentioned this idea in passing elsewhere, but no feedback has been received on it so time to give it its own topic, especially since I'm getting towards the point where a decision on this has to be made (otherwise a large amount of reworking will need to take place later to implement it).

Should arbitrary-shape/size trigger areas be allowed, rather than just rectangular ones? I would guess the primary use of it would be to allow circular trigger areas, but in general doing it this way would remove the need to add more supported shapes in future, since anything is allowed. It could also be used more creatively, for example, to create an exit with more than one region from which it can be entered (perhaps a large building that allows using a window, as well as a door). The only real downside (aside from an almost-negligable increase in file sizes) would be the potential for very annoying and illogical usage, but arguably that can be done (albeit not as complexly) even without such support. So for those of you who say no, it'd be good if you could post about why you feel that way.

Sure, I did kinda know something was coming (as a result of being asked for my address), but very appreciated nonetheless. (That also has to be the tidiest handwriting I've seen in a long time... especially compared to my own! xD)

Final decision: No.

Alright, so there are a lot of issues being brought up in relation to physics - so let's put this question out here.

Who thinks that we should entirely scrap the goal of "staying fairly close to NeoLemmix 1 physics", and instead reconsider every point while making NX2's physics - that's not to say that nothing will be exactly the same, but simply that each detail will be discussed and simply "Keep it as it is" will not be an overriding factor if good reasons are given to change something.

Yes, this will potentially break a lot of levels. But, some of the changes already being asked for already pose some risk of this.

(This might also be a good time to reconsider the possibility of a complete switch to hi-res; if we're going to be rebooting physics anyway, then doing this is much more logical than if we were trying to stay close to the original ones.)

If the answer is no, then this will also be taken as a sign that any changes should be kept to a minimum; because if we're going to be breaking stuff anyway, we may as well break everything at once rather than re-break it again and again later (and thus force constant updates, or levels that are no longer compatible with the newest versions). Do keep in mind that those who for whatever reason really want NX1's physics, could always continue to use NX1 - it will no longer be updated, sure, but I don't plan to make it vanish off the face of the earth if there are people who still want to use it.

Also, I'll make this very clear - if such a reboot occurs, there will be no OPTIONS - an argument can be made to have them with current physics. Such an argument cannot, in my opinion, be made when the entire physics set is being reconsidered more or less from scratch (obviously, using current ones as a starting point, but without the insistance on sticking to them as closely as possible).