[suggest[player]] Rewind to last assignment

[Gronkling]

At the moment we have rewinds for constant amounts of time, but maybe it would be good to have a key that rewinds to the frame of the previous skill assignment.

[Proxima]

Good idea, though I suggest a refinement. Since the most obvious use case is when you want to undo the most recent assignment, it would be good to have a hotkey that rewinds to the frame before the previous assignment.

If it's possible to press repeatedly to go back n assignments, this completely obsoletes savestates.

[IchoTolot]

The option is a very good idea!

If it's possible to press repeatedly to go back n assignments, this completely obsoletes savestates.

I disagree there. The savepoint can be a lot faster if it is set several assignments back! One button press against several there. The savepoint option is a customisable flexible case of that option.

[Gronkling]

Yeah I meant the frame before, so it's easier to reassign. And multiple presses should go to assignments before that like you suggested.
Maybe there could also be an option to go forwards to the next skill assignment in a replay too, though this would have pretty limited use.

[mobius]

excellent idea!
I also don't think this would make savestates obsolete however; they have other uses as well. [like saving one type of solution while trying another, of course there is saving a replay for that but save states are quicker].

[Proxima]

they have other uses as well. [like saving one type of solution while trying another].

Yes, that's a very good point.

[namida]

they have other uses as well. [like saving one type of solution while trying another].

Yes, that's a very good point.

It would be, if save states actually worked that way. It's actually somewhat of a misleading name - more accurate than "save state" and "load state", would be "remember current frame number" and "jump to memorized frame".

Anyway, in general, this is a good idea. I also had another somewhat similar idea: "Jump to next shrugging", which frameskips forward until a lemming becomes a shrugger. It'd be useful when building / platforming over long gaps.

[Gronkling]

Jumping 10 seconds basically does that already I think.

[namida]

Jumping 10 seconds basically does that already I think.

Yes, if you do it right after assigning a Platformer or a Builder. But for a Stacker; or if you execute the jump a bit later than the initial assignment time, it isn't so accurate.

[Gronkling]

Well I'm not opposed to the idea

[mobius]

they have other uses as well. [like saving one type of solution while trying another].

Yes, that's a very good point.

It would be, if save states actually worked that way. It's actually somewhat of a misleading name - more accurate than "save state" and "load state", would be "remember current frame number" and "jump to memorized frame".

Anyway, in general, this is a good idea. I also had another somewhat similar idea: "Jump to next shrugging", which frameskips forward until a lemming becomes a shrugger. It'd be useful when building / platforming over long gaps.

I suspected this but I guess I never tested this. So does this mean that if I save a state, then restart and doing something completely different from last play, then load state, it won't load it as it was when I saved?

[namida]

Yes, that is how it works. Which somewhat made sense back in the Lemmix days when we didn't have good rewind support, but that seems pointless now... so I've changed it for the next release so it acts more like an actual save state. Do be aware that it still won't carry over between levels, or even between attempts if the postview screen is invoked. I'll probably improve on the latter, though.

[namida]

Forgot to mention in this topic: The latest experimental release supports all of these changes (skip to last assignment, skip to next shruger, proper savestating).

If you find bugs in them or think there should be improvements to how they work, please make a new topic.