Doomsday Engine

With regard to materials, saving of their animation state should wait until material instances have their lifetimes scoped to usage contexts because each usage context has an entirely independent animation timeline.

Well, part of the reason I wrote the original subject title was because I considered that I may have more to add to it later (i.e if I thought of anything else that might be important for a save game to store).

Audio is another thing to consider (music and sounds); currently the music position isn't saved in a save game (currently if the loaded game uses the same music track currently playing, Dday simply continues playing it and if the loaded game uses a different music track to the one playing, Dday start's playing the different track from the beginning).

I suppose music in particular might become more of an issue if Dday eventually supports loop points with music.

Save games also do not store whether a playmusic console command that changes the music mid map, has been called (i.e via XG), always going back to the map info defined track.

Anyways, I'm going into specific examples of use now, which is outside the scope of this report.