Waterdude added the PlayerPartyStorage#addTaskForBattleEnd method to, among other things, safely open GUIs after a battle.

While trying it out I ran into a problem that the BattleControllerBase delivered by the Consumer does not know the outcome of the battle (who won, was it aborted, etc. [like the BattleEndEvent]). When asking about this we came to the conclusion that it might be a good idea for the battle controller to store results in itself when it generates them.