Lemmings Forums
NeoLemmix => Bugs & Suggestions => Closed => Topic started by: mobius on November 19, 2017, 03:40:08 AM
-
an (easy?) thing to implement: builder/platformer cueing like Lix has. You click builder multiple times on a single lemming and that lemming will automatically build X times. Thus allowing you to do that then FF a long time without worrying about builder running out of steps; or cueing then moving away and doing something else while they build.
I didn't mention stackers because they behave differently; well you can't keep stacking with one lemming in succession.
-
Unfortunately it's not really that easy to implement, basically because this means changing the code at a lot of different places:
- I have to add a new variable for lemmings, that store how many builders are queued
- I have to save this additional variable when saving the game state, so that they will still occur after backwards framesteps
- I have to change the replay code, because now it always saves a skill assignment when the lemming changes his work, not when the player clicked on it. This would mean that when loading a replay and modifying it, no skill queuing will ever happen.
So overall: A good suggestions, but not as simple to implement as one might think. I will certainly add this at some point, but don't expect it any time soon.
-
At least for now, could it not work similar to how skill assignments in general get queued? Perhaps even as simple as "don't clear a queued builder assignment if the lemming is currently building".
-
If people like this feature, I'm cool with it, but personally, I don't like builder queuing because I often find it very hard to assign builders to other lemmings when they are near any builder, as the game pretty much ALWAYS assigns the builder to one already building. That's been my experience with Lix anyways.
-
You can use priority invert to assign builder to a different lix.
-
At least for now, could it not work similar to how skill assignments in general get queued? Perhaps even as simple as "don't clear a queued builder assignment if the lemming is currently building".
This is kind of problematic, because this only allows queueing one builder, not multiple ones. So this would produce rather a lot of special-casing in the code without any real gain.
PS: Sorry for replying only now. I totally forgot about this topic.
-
At least for now, could it not work similar to how skill assignments in general get queued? Perhaps even as simple as "don't clear a queued builder assignment if the lemming is currently building".
This is kind of problematic, because this only allows queueing one builder, not multiple ones. So this would produce rather a lot of special-casing in the code without any real gain.
PS: Sorry for replying only now. I totally forgot about this topic.
True, it doesn't fully solve the issue, but it may be a good temporary measure. I don't know exactly how queueing skills is implemented so won't comment on ease of implementation of this.
However, one other thought that comes to mind - this (overall I mean, not just specifically my suggested temporary measure) should probably apply to Platformer as well as Builder, and possibly even to combinations of the two (eg. you could have a builder and queue a second builder, two platformers then a third builder). EDIT: I see that Platformer was already mentioned; my bad.
-
However, one other thought that comes to mind - this (overall I mean, not just specifically my suggested temporary measure) should probably apply to Platformer as well as Builder, and possibly even to combinations of the two (eg. you could have a builder and queue a second builder, two platformers then a third builder).
The trouble with allowing cross-skill queuing is that we mustn't disallow assigning builder to a platformer to make him switch immediately. If both are allowed, how do we distinguish them?
-
Good point. On that note though, I'd say there should be a way in general to cancel the queued assignments.
-
I've made a decision that NL will not be getting this feature. As nice as it is, it's quite a bit of work to implement, especially considering the need is also there to cancel the queue; and NeoLemmix has enough quality-of-life features that I think we can live without this one.