[Solved] Save/Load actions (GUI)

[darwin]

I have a complicated highly triggered map in my campaign. The player fights through 10 stages, and I would like to make it so that when they fail at a stage, it reloads automatically to the point start of that stage.

I considered pausing the game and forcing them to save manually, but then I discovered the Save Game and Load Game actions I've never used. I decided to play with them to see if it could solve my problem. I created this trigger:

• Melee Initialization
  • Events
    • Map initialization
  • Conditions
  • Actions
    • Wait 2.00 game-time seconds
    • Game - Display to (All players) the text: 3
    • Wait 2.00 game-time seconds
    • Game - Display to (All players) the text: 2
    • Wait 2.00 game-time seconds
    • Game - Display to (All players) the text: 1
    • Wait 2.00 game-time seconds
    • Game - Save game as TEST1.w3z and load TEST1.w3z (Skip scores)
    • Wait 2.00 game-time seconds
    • Game - Display to (All players) the text: 4
    • Wait 2.00 game-time seconds
    • Game - Display to (All players) the text: 5
    • Wait 2.00 game-time seconds
    • Game - Load TEST1.w3z (Skip scores)

What I anticipated, was to see something like this:

3
2
1
loading screen (when the game saves and reloads to this point)
4
5
loading screen
4
5
loading screen
4
5
loading screen
4
5

And so on.

Instead, what I saw was:

3
2
1
(loading screen)

Then nothing. The "4" and "5" never appeared. My map has a lot of repeating triggers. I don't know what would happen if the game saved, reloaded, and some of the triggers stopped working midway through.

Does anyone know how this works? Also, does it work in campaigns?

 

[Daffa]

Why not save at each stage start and use it as load point? Much easier in my mind.

 

[darwin]

Why not save at each stage start and use it as load point? Much easier in my mind.

If I understand you, I think that is what I'm trying to do.

My problem is that I don't understand the "save" and "load" actions. They don't appear to just save and load the game. If they did, the simple trigger I linked in my original post should have looped the "4" and "5" and kept printing them out.

 

[Dr Super Good]

Currently executing triggers probably do not save. Hence after the first load it breaks.

WC3 save/load is not very good for accurate state reproduction.

 

[darwin]

Ah, thanks Super Good. I suppose I could use the "add to queue" action to cause a save manually that won't interrupt other triggers.

This gives me hope, thanks.