What exactly do save states for the game NOT include? I've heard some hearsay and would like to know exactly what it entails. From this, it will help me determine if I need to employ a save system.

I've read somewhere that it doesn't save the state of randomized switches and playing wavs and speaking portraits.

this seems like a really big oversight.

So things like modified EUDs are all saved as well?

I'd say that depends on what part of the memory you're reading. The triggers are certainly untouched, wouldn't count on all variables though. If I were to guess I'd say currently active/blocked waits are also not saved.
My mentions were by no means comprehensive, and I'm not even sure because I never checked myself.
Probably Heinermann would know more of these things. Otherwise maybe you can just test the variables you need saved yourself?

Depends what you're doing with the EUD.

Switch states ARE saved. They are in a 96000 byte block that Starcraft just copies(and compresses) to save file.

Included in that 96000 block are

• Some map settings
  
• Player resources, scores, supply, upgrades, tech
  
• Message filter (chat)
  
• Current music ID
  
• Console index
  
• Alliance/Vision
  
• Timers
  
• Player Colors
  
• Next scenario name
  
• Saved Screen and Start Location positions
  
• Selections
  
• Some palette references
  
• Player settings/forces including names
  
• Leaderboard state
  
• Game pauses remaining
  
• Switch States
  
• Locations
  
• Timer pause state
  
• Upgrades/Tech in progress
  
• Other things
  

The state of the randomizer is also saved individually in another block. Triggers and their execution states are all copied.
Things like the AI are also saved in complete detail (such as AI "Captains", "Towns", "Controller" etc).

Things not saved:

• The timers for trigger loops and countdown timer (The timer itself is saved, just not the frame counter between each countdown).
  
• Pylon aura and selection circle images.
  
• All non-modifiable DAT file data.
  
• The position/state of a currently playing WAV or talking portrait. (Both of these are reasonable since they're handled by Storm and not Starcraft)
  
• The per-player global trigger flags and states.
  
• Trigger waits and wait states. However, this will resume the current action and re-execute the wait from the beginning. (untested)
  

Fun fact: You don't actually need a map to load a save file.

Post has been edited 1 time(s), last time on May 12 2011, 4:04 pm by Heinermann.