Hi Wolflight,
I’m not seeing anything in your code that I’d expect to affect the save system.
How are you running the tests, and how are you stopping them?
Side notes:
I’d recommend taking out the final FExecStringCommand(TEXT(“quit”)), and handle exiting elsewhere, since the current implementation would cause the editor to exit when any of the tests complete.
SetSuccess is optional, and will by default be set by the test framework based on whether any errors/warnings have been logged during the test run.
I suggest not caching the World, GameState, and GameMode for latent commands, and just Get them instead when necessary. Speaking from experience, there’s a non-zero risk they’ll get nulled between frames, which will cause Bad Things™ if you’re not always checking them before use.