Yeah, I'm also a bit iffy about the idea of erasing all future assignments for the same reasons. Additionally, it might be useful for the player to refer to the future assignments when correcting them - this could especially be the case if a user is attempting to repair a broken replay.

Quote from: WillLem on January 21, 2025, 11:04:27 PMBeyond this though, what would you suggest in terms of accounting for unmodified sets?

I'm on the fence between "fall back on the frozen-exiter behavior" vs "use the default style Sleeper sprite to fill the gap". I don't think this is significant enough to implement an option for; just pick one or the other and go with it.

Quote from: WillLem on January 21, 2025, 11:04:27 PMThis could be accounted for by specifically allowing Shimmier assignments to be queued. Saying that, I had a quick look and couldn't see anything specifically linking Shimmiers to queued assigments. I'll have a closer look when I get around to this specific feature, but if you happen to know whereabouts it is in the meantime I definitely think this one is worthwhile, given how aggressively it interprets user input.

It's not that any special behavior is explicitly coded, but rather that there's a lot of scenarios where there is only a one frame window to assign a shimmier (eg. slider->shimmier transition), and skill queueing is relied on to make this practical - even with framestepping, it's not the most convenient assignment to make otherwise.

Quote from: WillLem on January 21, 2025, 01:51:12 PM Sleeper lemming state - this state is entered when time runs out and the lemming reaches the exit. It's a mostly aesthetic state to replace the buggy-looking cluster of exiting lems, but it's also useful for simulating exit behaviour as these lems cannot be assigned to.

Make sure this plays nicely with custom lemming sprites, including those that have not been modified to account for it. EDIT: And also that the time might run out while lemmings are mid-exiting.

Quote from: WillLem on January 21, 2025, 01:51:12 PM Add option to deactivate skill queuing - another one that should definitely be optional as it's input-related.

Keep in mind that the assignment windows for some skills have been set under the assumption that skill queueing exists, in particular, niche transitions to Shimmier. Even though it's technically UI, I would argue this one leans a bit too much into physics to be messing with.

Quote from: WillLem on January 21, 2025, 01:51:12 PM Hotkey Config - Add Reset, Cancel and Save & Close buttons

There's already reset at least (or rather, three resets - one for each default layout option).

Quote from: WillLem on January 14, 2025, 11:13:34 PMMost other engines post-WinLemm have smoothed out the flickering cursor behaviour because it's no longer necessary with direction select (using the arrow keys to select a lemming fcaing a particular way) being a thing.

The reason this doesn't happen in NeoLemmix is not because it directly was fixed, but rather due to the underlying physics bug/detail that caused it being fixed. This happens because in DOS physics, a walker always moves one pixel ahead, and if he's inside a wall at this point, he then turns around but remains inside the wall. Thus - the behavior is simply a result of the lemming being inside the cursor region for exactly one frame. Likewise, he's only there for one frame because the pixel right inside the wall is under the cursor, but the pixel outside the wall is not - and because he turns around on this frame, he'll always be facing the desired direction. You just extend this to multiple lemmings coming into the cursor, each for one frame at a time, and there - the cursor itself is actually behaving 100% bug-free, but a physics bug (or at least a weird detail of physics) results in behavior that looks like a cursor bug.

I would be willing to bet that Lix is the same - it would happen there too if Lix replicated DOS's turn-around-at-wall physics, but it doesn't.

About two decades, I'd say - Lemmix made them both pretty much irrelevant. CustLemm especially, due to Lemmix being able to almost perfectly play CustLemm content (aside from early Lemmix missing some obscure glitches, as well as triggered traps in Lemmix resetting one frame faster than DOS/CustLemm - but this didn't get noticed even during the height of challenge runs (and I suspect that if we re-tried it on a fixed version of Lemmix, some replays might break but all the solutions would be reproducible) let alone when custom content began moving to Lemmix).

It's a standard MediaWiki feature I think. Check how Wikipedia or any other major wiki does it.

Infoboxes I believe are usually done via templates / transclusion. The templates themself have to be created.

I've fixed the image upload issue, as well as an intermittent login issue.

Alright, I've set up a wiki at: https://wiki.neolemmix.com/

Registration is required to edit pages, but not to simply view them.

It needs a logo - feel free to send me any suggestions. Otherwise - for all technical issues (including if there are additional addons / etc that people think should be installed, or if we get spam problems), let me know. For content, it's up to you guys.

Yeah, if we want to have the AI debate in general, let's make a seperate topic for that and keep this one more to the wiki idea (with any discussion of AI being solely about whether its use is allowed in writing the wiki - which really, for the reasons Icho explained, is going to be a defacto "yes" anyway; we aren't even going to know if an otherwise-good entry had assistance from AI).

(Also, FWIW, I didn't feel Silken's post was overly rude. The first line maybe a little bit, but the rest was all very much in the correct "attack the idea, not the poster" spirit.)

Anyway, it does indeed seem like there's at least some interest in the wiki so... yeah, sure, I'll spin one up at some point and we'll see where it goes. If it doesn't really go anywhere, we can always nuke it later.

Provide a couple of tunnel lengths, critically, including a single stroke. Make sure it has a marker for where the lemming will be when he starts the next stroke. Users can then chain these together as needed to create any length.

So... was there much interest in actually making this happen, or was it more just a case of "fun to discuss the idea"? As mentioned, I am happy to handle the hosting / setup / technical maintenance for this if there's interest. (I would want to see at least a few people who want to contribute to it (rather than just want it to exist) who are interested.)

Quote from: WillLem on January 11, 2025, 12:09:13 AMHow much work would it be to make NL 64 bit now that GR32 has been updated? Or, is it still not feasible?

Probably very easy, if GR32 is indeed compatible (and performs as well - or better than - 32 bit).

The only difference that would arise with regards to file handling is the fact that some OSes (including Linux) have case-sensitive filenames, ie: "steel_01.png" and "Steel_01.png" are two different names (and you could even have both existing at once). However, for the exact reason that a Linux port / clone could happen, this is why I've always advised to use lowercase letters in style / piece names.

If there's a desire for one, I can set one up hosted on the same server as Lemmings Forums using MediaWiki or any similar software. Makes more sense to do that than use a third party service full of ads.

However, I do want to be clear that I'm not likely to contribute much content-wise (I might write up some articles on file formats but that's probably about it). I'll handle the technical stuff and it will be up to the community to write the articles (and to make decisions on the general formatting, what to cover, etc).

I also have no issue with AI being used as long as it's being proofread, fact checked and edited by a human rather than just blindly copy pasted. (In other words: Use it as one of many tools; not as the sole source of content.) Of course, ultimately that too is a decision for the community to make, and this statement is just my own input on it (rather than an actual ruling).

Don't block the functionality under any circumstances. Up to you what circumstances you feel justify showing a warning to the user before activating the feature.