Error: "Attempting to resetState while current state is destroyed" (5.6.0)

[moxie-coder]

I would get a “Attempting to resetState while current state is destroyed” error from legacy code, I don’t really get how it works now with the latest flixel

[Geokureli]

can you show how you're switching states?

@CaptainBaldi had the same issue, in the discord, maybe there's a similar solution

[moxie-coder]

same sort of thing he was doing, I’ll try the solution you mentioned in the discord

[Geokureli]

for posterity can you share the relevant code, anyway?

[moxie-coder]

forgot to send it, here

	public static function switchState(nextState:FlxState) {
		// Custom made Trans in
		var curState:Dynamic = FlxG.state;
		var leState:MusicBeatState = curState;
		if(!FlxTransitionableState.skipNextTransIn) {
			leState.openSubState(new CustomFadeTransition(0.6, false));
			if(nextState == FlxG.state) {
				CustomFadeTransition.finishCallback = function() {
					FlxG.resetState();
				};
				//trace('resetted');
			} else {
				CustomFadeTransition.finishCallback = function() {
					FlxG.switchState(nextState);
				};
				//trace('changed state');
			}
			return;
		}
		FlxTransitionableState.skipNextTransIn = false;
		FlxG.switchState(nextState);
	}

	public static function resetState() {
		MusicBeatState.switchState(FlxG.state);
	}

[Geokureli]

for anyone else doing stuff like this, the recommend fix was to override startOutro in your state for handling outro transitions rather than doing something like this

[Geokureli]

related: ShadowMario/FNF-PsychEngine#14126