Selecting original SOD causes Episode 3 to load instead

[Former user]

I downloaded v1.2.2 on my desktop and found that when I tried to resume my original SOD savegame, it loaded up one of the episodes. Restarting the game, and comparing to the other two mission packs, showed that it was loading the Episode 3 IWAD instead of the original SOD. I did not have this problem with v1.2.1 on my laptop.

[Braden Obrzut]

So does starting a new game cause the mission pack to load or just the save?

If a new game, did you reinstall the game on Steam? If so, start the game through steam on the original mission and quit once you get to the menu.

[Former user]

That was actually how I figured out it was Episode 3: after loading the game and realizing the textures, sounds, and so forth were all wrong, I started a new game, and that gave me something completely different from what I'd played a few days earlier. Opening the other two mission packs allowed me to determine it was Episode 3.

Deleting local content and reinstalling through Steam did not change this behaviour. Re-opening the game in Steam, though, did. Which I don't think I understand, but okay.

[Braden Obrzut]

Ahh, so this is the known issue. Steam ships with the game configured for episode 3. Since vanilla includes no mod support, how it loads the other missions actually consists of renaming the sd3 files into sod. By starting the game in Steam first, the sod files are reset to the original mission.

[Former user]

Have you thought about loading the .sd1 files instead of .sod for Spear of Destiny? .sod could be used as a fallback if there are no .sd1 files.

[Braden Obrzut]

I have. I'm going to do something effectively like that when I get the chance. Since my plan to just fix the filenames physically failed, I plan to have the renames be stored in a virtual file system. This way from ECWolf's point of view the files are named .sod and the hack can be contained without potentially causing further issues with multiplayer.