Change Details

This means that if you add something to the Callqueue, it will actually still be called after a world (re)load, which to my knowledge is never actually wanted. This also affects GameStateTransitions::RequestScenarioChangeTransition(), which is called by game::PlayGameConfig(). In PlayGameConfig(), this can be avoided by calling GetGame().GetCallqueue().Clear() if the transition is successful.

This means that if you add something to the Callqueue, it will actually still be called after a world (re)load, which to my knowledge is never actually wanted. This also affects GameStateTransitions::RequestScenarioChangeTransition(), which is called by game::PlayGameConfig(). In e. g. PlayGameConfig(), this could be avoided by calling GetGame().GetCallqueue().Clear() if the transition is successful.

This means that if you add something to the Callqueue, it will actually still be called after a world (re)load, which to my knowledge is never actually wanted. This also affects GameStateTransitions::RequestScenarioChangeTransition(), which is called by game::PlayGameConfig(). In e. g. PlayGameConfig(), this canould be avoided by calling GetGame().GetCallqueue().Clear() if the transition is successful.