There has been a few cases of CleanTalk causing problems for legitimate users of the site - two users have reported their legitimate posts being outright blocked (in one case this was due to a VPN, the other one has no explanation whatsoever), and we've also had a few cases where posts were flagged for moderator approval despite having no need to be (I'm a bit less concerned about that last part - I consider that to be a tolerable side effect, it's the outright blocking that concerns me).

I raised a few potential solutions on the staff board, and am now bringing them into public discussion.

Option 1 - Keep as-is, accept it will cause problems sometimes
Self-explanatory. I really don't like this option - aside from that it's going to frustrate users who have done nothing wrong, another concern is that new users may be attempting to sign up, running into problems, and we never know because they never reach out to us, so they just give up and don't join.

Option 2 - Use CleanTalk with altered settings / customizations
The main ideas here are (a) disable the filter that stops suspected spambots from even accessing the site (even to read it), and (b) only apply the spam check to posts from new users (with the "what counts as a new user" being a to-be-discussed point). I was a bit hesitant about this due to the amount of work that would be involved, but it actually looks like the plugin has at least rudimentary features to help with this. The problem with this approach is that it still doesn't really help much with users who don't even manage to register (if they do manage to register and attempt but their posts get outright blocked, I'll at least see them in the CleanTalk admin panel - but a blocked registration attempt is literally impossible to distinguish spam attempts from legitimate ones, especially at a quick glance).

Option 3 - Mod/admin approval of all registrations and posts from new users
The idea for this one is - get rid of CleanTalk, and rely on human approval for new users. Admin approval would be needed for new registrations, and mod or admin approval would be needed for their first few posts. The biggest problem here is how to handle a case of "spambot makes account, never posts, just spams via PM" (while also being mindful of that there are several legitimate users who don't ever post publicly, but do communicate with other users via PM). Maybe this isn't a big enough concern to worry about right now - I haven't received any reports of PM spam so far.

Option 4 - Revert to old setup, deal with spam as it happens
And the last option is simply to go back to minimal anti-spam measures (just security questions etc - not much point in CAPTCHA these days, it's trivial for AI to defeat it), and accept that spam attacks will happen once in a while, and that they're annoying but not really the end of the world - users here should be savvy enough to identify and disregard them, so the issue is yeah, really just that they're annoying.

I was initially favoring option #3, but after seeing that the CleanTalk plugin already has some features that might help get a good enough setup of option #2, I'm leaning more towards that. Discussion of this matter on the Staff Board also, where other staff did respond, was leaning towards preferring option 2. As an interim measure I've already implemented option #2 part (a) (disabling the filter that blocks the site entirely for suspected spambots) and will see what difference that makes, if any.

And for any legitimate users trying to sign up who are encountering issues - please, reach out to us. You can contact us on the Lemmings Forums Discord, or on the #lix IRC channel on QuakeNet.

Hi all,

I have decided to look into a new host for Lemmings Forums (and related sites) for a couple of reasons.

The first one is that I have noticed that several other comparable hosting providers (reputable ones, not dodgy no-names) provide comparable service at around half the price. While they lack some of the advanced features of DigitalOcean, these advanced features are ones that I don't actually use (some of them I don't even know what they're used for beyond vague concepts) and the sites will be fine without. Thus, by switching, I can either cut the costs, or alternatively, get a much more powerful server for the same cost.

The second is that, while I realise it's impossible to 100% avoid, especially while remaining practical, I wish to minimize any spending that funds the US (which in practice means don't buy services from US companies, as they pay tax to the US government). Moving away from a US-based host is a step towards this goal. The reasons for this are outside the scope of subjects we would usually discuss on this site, but I'm also sure you all can guess exactly what they are. It's most likely I'll go with a Europe-based option instead (partly due to most of the site's userbase being in Europe or the UK, so it makes sense to have the server located there too), but there's also one NZ-based option I've been looking at too, and I'm also open to Australian options if any good ones come up.

To avoid doubt: This does NOT mean US-based users are no longer welcome here. American people are not the problem, and are not in any way a "target" of this action. If you are welcome here today, you are still welcome here after the move (assuming you don't suddenly start spamming the forum between now and then or anything like that, of course). Nor will anyone be banned for not following the same course of action themself - this is what I am choosing to do, and I am sharing it in order to explain how it will affect the site; that's all.

No final decisions on who the new host will be or when we'll move have been made at this stage, but I tend to move pretty fast once I've decided on something, so don't be surprised if it happens within the week.

In terms of impact on site use: You can expect a small amount of downtime, but that's it. As this will be a 100% planned move, unlike the last one that occurred due to problems with the server, it should go a lot more smoothly than the last one. This also means that for a significant portion of the move, instead of the site being completely down, it should be able to remain online in "read-only" mode.

Or rather, has been since May, but I only just found out about it.

I don't personally have it - a trustworthy member of the community managed to secure it. Since they haven't spoken about it, and I only found out when I reached out to "the owner" earlier since I noticed it was no longer being used even to serve ads (literally no DNS entries), I can assume they don't want it widely known that they have it; so I won't say who it is. (I initially made this topic for the staff board before realising there was no reason to confine it to there; and even then, I kept the person anonymous.) They can reveal it themselves if they wish to.

I've coordinated with them to set up a redirect to a dedicated topic explaining why .com links no longer work; I've closed that topic since it's intended to serve solely as a post we can redirect such links to, and started this one because I'm sure the community will want to discuss this. There hasn't been any discussion about transferring ownership or anything like that, basically just them confirming they have it and coordinating to set up the redirect.

Hi,

You've probably ended up here because you followed a link that points to a topic or attachment on LemmingsForums.com.

Although we have recently been able to secure the LemmingsForums.com domain name again, we are not able to correctly match old-site links to current-site topics via any automated algorithm, and there are far too many posts to even consider doing it manually. This is due to the way posts were migrated - we were not able to access an up-to-date database backup (only an older one), and therefore, had to resort to scraping every topic via a web crawler instead. Therefore, we have elected to have any attempts to access LemmingsForums.com result in redirection to this topic.

If you were just trying to get to Lemmings Forums in general - congratulations, you're here! You can click the logo in the top-left corner of this page, to go to the front page of the site. If you were a member of Lemmings Forums during the LemmingsForums.com era, your old account might still exist here - doesn't hurt to try (please note that your PMs will not have been preserved). Although posts from even-older iterations of the forums have been preserved on the current site, accounts from older iterations have not.

If you have a general idea of what the topic/post you were looking for is, you may be able to find it by using the Search bar at the top of the page.

As reCaptcha and security questions are no longer effective, and a secret password is frustrating for new users, I've now added CleanTalk anti-spam to the forums. We'll see how well this works, but it should be completely unobtrusive.

If any legitimate would-be users are having trouble registering (or posting), please reach out on the Lemmings Forums Discord or the #lix IRC channel on QuakeNet.

We had an incident the other day involving a large (by our standards) wave of spambots.

As a temporary measure to combat this, I have changed the question when registering an account to one where the answer cannot be found in public - instead, it's basically a "password" that must be obtained from site staff (possibly via another member). To be clear - this is purely an anti-spambot measure, and the password will pretty much be given to anyone as long as we're sure they're a human and not a spambot. When the site prompts people for this, it will advise them to ask on either the Lemmings Forums Discord or the #lix IRC channel.

Staff members who are not already aware of the password can find it in the topic about the spam wave on the staff board. If a non-staff member needs the password for the sake of passing on to a friend who is trying to register, you are welcome to ask any of us for it - again, it's purely a spambot filter, and I have no issue with humans sharing it with each other. However, please do NOT post it publicly. If sharing it with someone, do so via a private communications channel (eg. DMs on a social media site, or email).

On a side note, it was brought to my attention that users with no posts were being hit with this prompt every time they tried to send a PM. This should no longer be happening; nor should new users have to answer the question a second time when making their first post. It should now appear once during registration, and never again after that. (However, the wording for SMF's setting regarding this was a bit ambiguous, and it may in fact have the opposite result - now making everyone, except mods / admins, answer the question every time they post, even if they've posted before. My testing suggests this is not the case, and that it's working as intended, but please let me know if this is not the case.)

I will be looking into a better means of dealing with this - there are a few good open-source anti-spam solutions out there that go way beyond just a security question (viable but annoying) or a captcha (basically useless these days), and I'd be surprised if SMF doesn't have plugins to integrate with them. The password-style security question is just a temporary measure until that happens.

A new update to SMF has been released, so the forums will need to be updated to it at some point. As always, due to the customizations and the use of addons (some of which have had to be installed manually and modified to be 2.1 compatible), it's not going to be as straightforward as just running the auto-update; but I'll look at sorting this update in the near future.

At this time I have no expected dates or other further details to share.

SendGrid, the service used to send emails from the site, is discontinuing their free plan in the near future.

Rather than just find a substitute (or use their paid service), I've opted to go for a self-hosted solution here. I've tested this and all appears to be working, however please note that as a result of this change, emails from the site may have a higher risk of going to Spam and/or being flagged as "unusual" for a little while.

This has been reported in other topics (or maybe Discord, or maybe both) in the past.

Making a topic about it, also so that I can save a record from the error log here:

Quote<username redacted>
<IP address redacted>
<session ID redacted>
https://www.lemmingsforums.net/index.php?action=pm;sa=send2
/home/lemmingsforums.net/www/public/Sources/Errors.php (Line 234)

Backtrace information

Type of error: Undefined
Error message
2: Undefined array key "attachments_limit_per_post"

Hi all,

We recently had an incident where a newcomer posted fan art that pushed the lines in regards to NSFW content - it featured a "drunkard" lemming who among other things was not wearing pants (but the genitals were censored with a black box), who also had a nose that closely resembled genitalia (this was not censored in any way).

Simon initially removed this image. After some discussion between myself and him, the decision was reached to restore it, but to put the image inside a ZIP file so that no preview is shown, and put a clear "not safe for work" warning in the filename. This was primarily due to my input; my reasoning being that we have shared content of a similar level between existing members before (for example, drawings that resemble - or occasionally, just outright are - dicks, in the Jackbox topics). Simon also noted when restoring it, that the image "is edgy, but is honest fan art".

As part of this discussion, the idea also came up that we should seek feedback from the wider userbase as to how to handle such material going forward.

I do want to clear up some things right here first: There's definitely going to be limits as to what we allow. Don't expect the site to ever have a "share your favorite porn videos" topic or anything like that - Lemmings Forums absolutely is not a porn site. However, when it comes to content where the primary intent is artistic and/or comedic in nature, rather than sexual, I'm much more open to - and personally, would prefer to lean on the side of - leniency, subject to such content being hidden behind NSFW warnings (ie: no image previews for attachments, so put them in a ZIP or similar; or if they're embedded, then put them inside spoiler tags).

How do other users feel on this subject? While higher priority will be given to the thoughts of long-time members, input from newer users will be considered as well.

To be clear, I don't have any need for this feature myself. I'm bringing it up on behalf of discussions I've seen elsewhere online.

From what I've seen on a few Reddit etc posts, the Windows dialogs used for level select, options, replay editor, popup messages, etc don't play nicely with the Steam Deck when in game mode (rather than desktop mode), so it may be worthwhile looking into non-Windows-dialog replacements, even if they don't offer the full functionality.

Potential issue: How does a user who can't use these menus, activate this mode for the first time? (Perhaps try to autodetect Steam Deck, and enable the option by default? It isn't the end of the world if it gets disabled again by mistake - the user can always switch to desktop mode to change back.)

It is likely this could be tested using a handheld device running Bazzite (or something that has the same limitations as a handheld, ie: has a controller and touchscreen, but no keyboard or mouse), as that's very similar to Steam OS.

Subject came up in Discord, realised I couldn't easily find any documentation of the algorithm on Google despite being sure I'd seen it before, managed to track it down. Posted here for reference.

Source: The source code to "LemGen", linked under "Other game tools" on the Lemmings Universe downloads page. This is from comments in LCP100S0.BAS (which is the only source code file).

Quote'-----------------------------------------------------------------------------
'
' HOW THE LEMMINGS CODES ARE PUT TOGETHER:
' =======================================
'
' Let us number the characters in the codes as follows: 0123456789
'
' This example of the first 20 level numbers are taken from my 100% codes
' from the original Lemmings version:
'
'    Level   Real order          Real order            Logical order
'   number
'           0123456 78 9   vertically aligned 78 9      0123456 78 9
'
'       1:  CAJJLDL BC S       CAJJLDL        BC S      AJJLDLC BC S
'       2:  IJJLDLC CC L        IJJLDLC       CC L      IJJLDLC CC L
'       3:  NJLDLCA DC Y         NJLDLCA      DC Y      ANJLDLC DC Y
'       4:  JLDLCIN EC R          JLDLCIN     EC R      INJLDLC EC R
'       5:  LDLCAJN FC K           LDLCAJN    FC K      AJNLDLC FC K
'       6:  DLCIJNL GC T            DLCIJNL   GC T      IJNLDLC GC T
'       7:  LCANNLD HC Q             LCANNLD  HC Q      ANNLDLC HC Q
'       8:  CINNLDL IC J              CINNLDL IC J      INNLDLC IC J
'       9:  CAJJMDL JC L       CAJJMDL        JC L      AJJMDLC JC L
'      10:  IJJMDLC KC U        IJJMDLC       KC U      IJJMDLC KC U
'      11:  NJMDLCA LC R         NJMDLCA      LC R      ANJMDLC LC R
'      12:  JMDLCIN MC K          JMDLCIN     MC K      INJMDLC MC K
'      13:  MDLCAJN NC T           MDLCAJN    NC T      AJNMDLC NC T
'      14:  DLCIJNM OC M            DLCIJNM   OC M      IJNMDLC OC M
'      15:  LCANNMD PC J             LCANNMD  PC J      ANNMDLC PC J
'      16:  CINNMDL QC S              CINNMDL QC S      INNMDLC QC S
'      17:  CAJJLFL BD V       CAJJLFL        BD V      AJJLFLC BD V
'      18:  IJJLFLC CD O        IJJLFLC       CD O      IJJLFLC CD O
'      19:  NJLFLCA DD L         NJLFLCA      DD L      ANJLFLC DD L
'      20:  JLFLCIN ED U          JLFLCIN     ED U      INJLFLC ED U
'
' We can observe block-wise rotating of the first 7 characters:
' Each block of 8 levels rotate 7 times.  Note that the codes for levels
' 8,9 and 16,17 etc. all are rotated equally:  No change between 8 and 9 etc.
'
' We can also see, that character 7 and 8 must contain level-number
' information, because of the way those values change.
'
' Character 9 could be a checksum, which is an obvious idea to be checked.
'
' Coming back to the first 7 characters:
' It is not hard to decide where to start the first logical character. In the
' "verticalli aligned" column, we see a column with AIAIAIAI etc., and the
' column to the right of that one, we see JJNNJJNN etc.  It looks as if the
' level number is hidden in there too in a binary way:  The least significant
' bit on the left.  So let's rotate these seven characters until this supposed
' least significant bit is placed first, and we have our logical order.
' The code looks much more structured now!
'
' Looking at codes with percent information for a certain level (which you
' can try yourself and which I don't show here), we see that this extra
' information is also changing those seven characters in a similar way as
' the level-number information does.  There are some exceptions here with
' these percentages, which are due to what I call "spurious bits".
'
'- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
'
' Some conclusions and other observations:
'
' characters 0..6 : bit-coded rotating level + percentage info,
' characters 7    : hex Level low  4 bits
' characters 8    : hex Level high 4 bits (the highest bit will always be 0)
' characters 9    : hex checksum of chars[1..9]
'
' More results:
'
' Different Lemmings games use different letter ranges for each character:
' The different characters, counted the logical way as in the last column in
' in the table above, start at different  characters for different games.
' Let us call these starting values "base characters".  It is not hard to
' guess what those might be, if you look at the character ranges of each
' column in the "logical order" codes separately.  I found these "bases":
'
'                                   Logical order 0123456789
'                                                 ----------
' Lemmings, Xmas91, Xmas92, COVOX, Prima Bonus:   AJHLDHBBCJ
' Oh No!, Oh No! demo:                            AHPTDHBBAD
' Holiday 1993, Holiday 1993 demo:                AJHLDHBBAD
' Holiday 1994, Holiday 1994 demo:                AJPLDHBBCD
' Lemmings demo, old version. (Not found by me):  EHPVLXDHIJ <- see below
'
' If we forget the old demo of the original Lemmings version with its
' incomplete implementation of the coding scheme, we can see that only
' characters 1, 2, 3, 8 AND 9 use different bases.
'
' These base characters are updated to a code by adding a nibble to each
' character, which carry several different bit-wise informations.
' (A nibble is a 4 bit unit, a hecadecimal digit, a number between 0 and 15.)
' The first 7 updated characters are then rotated somehow for each level.
' Expect only illegal codes with base character (3), especially with Oh No!
' (The old original Lemmings demo would create a lot more illegal codes then.)
'
' In 1999 I found exactly the above strings (AJHLDHBBCJ etc.) in the expanded
' exe-files of each game.  These strings were exactly the same as what I
' constructed in 1994 and 1999, except for old Lemmings demo:
'
'- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
'
' Before I knew about the incompleteness of the old Lemmings demo, which does
' not use the percentages of rescued lemmings, I used the same scheme as with
' the other games, and got for 100% rescued lemmings following base characters
' Lemmings demo, old version, my first guess:     GHNVMTCHIJ <- not used here
'
' Because percentage is not used there, and because I found the string
' EHPVLXDHIJ in the expanded exe file, where all other games have strings,
' matching my already found base characters, I used that info instead.
' This meant, that I needed to make my spurous bits fixed to 33, (= hex 21).
'
'- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
'
' Checksum calculation is very eazy:
' The low nibble of the sum of the ASCII values of the first 9 characters
' is to be added to the base character for the checksum.  That is it.
'
'-----------------------------------------------------------------------------
'
' The description of each bit in the nibbles of the 7 "rotating" characters:
'
' The table below shows following:
'
' Line 1:  Nibble numbers, which are the same as the logical order numbers.
' ------
' Line 2:  Bit numbers of the 4 bits in each nibble, as usual.
' Line 3:  Bit values  of the 4 bits in each nibble, as usual: = 2^bit_number
'
' Line 4:  The bit descriptions of each bit in each nibble, where:
'     0  = fixed bitvalue: must be zero, otherwise the code is not accepted!
'     Ln = level bits: L6 is most significant, L0 is least significant
'     %n = previous percentage bits: %6 is most-, %0 is least significant
'     Sn = spurious bits: S6 is used here as most, S0 as least significant
'
' nibble 0 | nibble 1 | nibble 2 | nibble 3  | nibble 4 | nibble 5 | nibble 6
'----------|----------|----------|-----------|----------|----------|---------
' 3  2  1 0| 3  2 1  0|3  2  1  0| 3  2  1  0| 3 2  1  0|3  2  1  0|3  2 1  0
' 8  4  2 1| 8  4 2  1|8  4  2  1| 8  4  2  1| 8 4  2  1|8  4  2  1|8  4 2  1
'          |          |          |           |          |          |
'L0 %0 S0 0|S1 L1 0 %1|0 L2 %2 S2|S4 S3 %3 L3|%4 0 L4 S5|0 %5 S6 L5|0 L6 0 %6
'       |    |                     |  |                |
'       |    +---------------------+--+----------------|---> never seen as 1
'       +----------------------------------------------+---> old Demo: make 1
'
'-----------------------------------------------------------------------------

Just in case the worst happens and the US-based domain name and/or servers suddenly become unavailable, unsafe or otherwise an issue, I have take some precautionary steps to hopefully get the site up and running again as quickly as possible in such an event.

The first is that backups are now being taken weekly instead of monthly, and an increased number of prior backups will be preserved. (I will also be looking into keeping a copy of them locally rather than only on a seperate cloud service -  note that the local backups will be as well as the cloud ones, not instead of them - but I have not put this in place yet at the time of this post.)

Secondly, I have registered the domain name https://www.lemmingsforums.nz/ (based here in New Zealand) as a backup option just in case. At present it simply redirects to .net, but if for any reason we can't continue to use the .net domain, the .nz one can be used to replace it. (In particular, if things really go to shit in the US and the site becomes unavailable around the same time - definitely check the .nz one. In the event something happens but I can't get the site up on a new server right away - and taking into account that neither Discord nor QuakeNet may necesserially be available in such a scenario either - I will likely use that URL to get an "I'm working on it" message out.)

I don't think it actually will come to any of this, but with how rapidly the situation has been deteriorating in the US (where all the hosting etc is based, despite me myself being in New Zealand), I feel it necessary to at least have some precautions in place.

For similar reasons, I would also like to remind all US-based users that public posts on the site are obviously visible on the clear web, but also, that private messages do not have any encryption (unless you and the person you're messaging are manually encrypting and decrypting your messages to each other) - if access to the server (or backups) were to be granted to government agencies, they would have no difficulty ascertaining the contents of private messages. As such, anything that may be sensitive subjects in light of recent US events may be wise to discuss elsewhere. To avoid any doubt - I am not saying you are prohibited or discouraged-by-rule from discussing such subjects in your PMs to other users, just be mindful of potential privacy / safety concerns if you or the person you are messaging is in the US.

Unlike the three years between 12.12.0 and 12.13.0, this update follows just a few months behind 12.13.0 - and this will be NeoLemmix's final version, with no further updates other than to user-created custom styles. (However, there is a fork, NeoLemmix Community Edition, that strives to continue improving UI aspects of NeoLemmix while retaining 100% physics / data / replay compatibility with official NeoLemmix 12.14.0.)

There are no major new features here; this update simply fixes a couple of physics bugs relating to the Fencer and the Shimmier. As such there is also no corresponding editor update; the existing version will still work.

Changelog, V12.13.0 -> V12.14.0

> Fixed bug: Sliders can be assigned Shimmiers right at the bottom of the level, and shimmy under the level.
> Fixed bug: Fencers sometimes stop at steel without turning around when they should turn.

Download: https://www.neolemmix.com/download.php?id=600 (permalink to V12.14.0)
Styles: https://www.neolemmix.com/download.php?program=52 (link will always point to the latest styles download)
Editor: https://www.neolemmix.com/download.php?id=591 (permalink to V1.42)
Alternatively - the SuperLemmix editor is based off the NeoLemmix editor and retains NeoLemmix support, but is actively being developed and has some useful new features.

You do not need to download the styles here - you can download them as needed in-game instead. This link is provided for the convenience of users who wish to download all styles in one go and/or do not wish to enable online features in NeoLemmix. Additionally, the L1 and ONML styles are included in the main download.

Game source code (Delphi): https://bitbucket.org/namida42/neolemmixplayer/
Editor source code (C#): https://bitbucket.org/namida42/neolemmixeditor/

If you are upgrading from V12.12.X or earlier, please set up in a new folder (you can copy over your Levels and Settings folders). If you are upgrading from V12.13.0 or from V12.14.0-RC builds, you can just extract over the top of it but in this case do not extract the "settings" folder (otherwise you will lose your last-updated timestamps for the style manager). NeoLemmix will show a warning message if upgrading from V12.13.0 this way, but it is safe to ignore it.

What do I need to do with my existing content?

As is always the case with a major version update, you should run a mass replay check on your levels to verify that your solutions still work, and fix any replays (or levels, if necessary) that have broken. Breakage is only likely to occur in levels that use the Fencer (there is also a Shimmier fix but it is extremely unlikely that any real-world replays, especially intended solution ones, have made use of the relevant bug).

Custom styles should not need any special attention for this update.

Hi all,

Just wanted to mention that, with the SMF 2.1 upgrade and the fact that the site now supports notifications for new quotes / replies to topics / etc, it would be very preferable if people edit their post if they need to make changes, rather than deleting it and then posting another almost-identical post. (This is doubly frustrating for site staff, who may very well click these notifications only to - maybe without realising it - end up in a topic on the Recycle Bin board.)

(At least at this stage) I'm not going to set any outright rules about this, it's more just a matter I'm raising as another user (rather than as admin).

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.

As per the cutoff date for bug reports indicated earlier, no new bug reports will be accepted for NL three months after the release date of V12.13.0, or in other words, one month from today.

(Bug reports are already limited to bugs that either were introduced in 12.13.0, or cause data loss / crashes.)

I won't have time to look into what happened here until about 12 hours from now, but I am aware of it. I rebooted the server and that seems to have sorted it for now.

I've mentioned a couple of times on Discord that I was working on a Commander Keen fangame.

I've now released it. It's based on Keens 4-6 and is a bit more like "level pack on a custom engine with some customized game features" (hm, where have we heard that before? ) than a full-on fangame.

More info over at the Public Commander Keen Forum: https://pckf.com/viewtopic.php?t=17958

Download link: https://nv.wtf/GalaxyReimagined_1.0.3.0.zip

This is unrelated to the recent issues. The monthly limit for the email provider the site uses has been reached; seems there was a sudden spike yesterday / overnight. I'm not sure at this stage whether it's just a spike in genuine emails, something fishy, or (most likely) emails sent during the course of me working on the 2.1 upgrade on a local server.

I won't get a chance to investigate this until later today. In the meantime, keep an eye on your PMs and watched topics manually, and if anyone is trying to register and not able to verify, contact an admin via Discord or IRC and we can activate your account for you.