Ability to define game / mod files directory

Advanced Wolfenstein 3D source port based upon Wolf4SDL and ZDoom.
[Home] [Download] [HG builds (Win)] [HG builds (Mac)] [Wiki] [Repo]

Moderator: Blzut3

Guest

Ability to define game / mod files directory

Post by Guest »

Having one large unorganized messy dump of every file in the same directory as ecwolf is antiquated. Please provide the ability to define directories for game files/mods placed in their own individual folders like every other respectable source port does either via command line parameter or through a config file. This basic feature is availble on gzdoom, eduke32, quakespasm, yamagi, the force engine, etc, etc. This also allows for much easier troubleshooting and removal or relocation of files if required.

Thanks for your consideration.
Blzut3
Developer
Developer
Posts: 498
Joined: Sun Jan 24, 2010 22:21

Re: Ability to define game / mod files directory

Post by Blzut3 »

It is in the cfg. Key is BaseDataPaths.
Why
Posts: 6
Joined: Thu Nov 28, 2024 21:16

Re: Ability to define game / mod files directory

Post by Why »

Blzut3 wrote: Fri Nov 29, 2024 23:51 It is in the cfg. Key is BaseDataPaths.
Thanks.

I found the config file, the appdata/roaming directory is the default for some reason... Anyways, I added 4 different directories to all 4 of the official games (Wolfenstein 3D, Spear Of Destiny, Mission 2 Return To Danger and Mission 3 Ultimate Challange) to the key you mentioned and only Wolfenstein 3D and Spear Of Destiny are being detected when ecwolf is launched. Mission 2 and Mission 3 are missing from the launcher list. Even if I add command line parameters of "--data sd2" and "--data sd3" to ecwolf.exe shortcuts I still only have the option to launch either of the first two games. Any idea what the problem is?
Blzut3
Developer
Developer
Posts: 498
Joined: Sun Jan 24, 2010 22:21

Re: Ability to define game / mod files directory

Post by Blzut3 »

Works for me, although there is some search logic related to the mission packs that I could imagine being tripped up for some reason. Do they work for you if they're in the same directory as sod?
Why wrote: Sat Nov 30, 2024 10:50 I found the config file, the appdata/roaming directory is the default for some reason...
That's the location Microsoft has recommended putting config files since at least NT4/98 but likely even earlier. Of course developers ignored that recommendation until Vista came along and made other methods unreliable if the user doesn't know about all the quirks.
Why
Posts: 6
Joined: Thu Nov 28, 2024 21:16

Re: Ability to define game / mod files directory

Post by Why »

Blzut3 wrote: Sun Dec 01, 2024 1:28 Works for me, although there is some search logic related to the mission packs that I could imagine being tripped up for some reason. Do they work for you if they're in the same directory as sod?
Why wrote: Sat Nov 30, 2024 10:50 I found the config file, the appdata/roaming directory is the default for some reason...
That's the location Microsoft has recommended putting config files since at least NT4/98 but likely even earlier. Of course developers ignored that recommendation until Vista came along and made other methods unreliable if the user doesn't know about all the quirks.
Microshaft also seems to think that the abominations they have released since 8.1 are good operating systems so I wouldn't put too much weight into that. Personally I prefer everything for a program to be inside a single portable install directory rather than a mess spread acroas the entire OS so you don't have to go searching for things and can easily move it but that's besides the point.

Either way, I figured out what the problem was. Apparently since microshaft acquired zenimax which is a conglomerate that owns bethesda that once bought id software they have since removed the mission packs from the gog install that I purchased. Needless to say the mission packs are now abandonware since they aren't any longer commercialy available for purchase. So naturally I downloaded them. During the troubleshooting process and to create some batch scripts to run mods I had to enable windows to "show extensions for known file types" since they are disabled by default.... It turns out that whoever uploaded the mission packs for download also thought it would be wise to change all of the extensions to ".sod" for some unexplainable reason....... So obvioisly ecwolf was going to only detect both games as Spear Of Destiny. As soon as they were all changed back to ".sd2" and ".sd3" respectively they were instantly detected by the ecwolf launcher.

So this is solved but you might want to leave it open for anyone else troubleshooting the same problem.
Post Reply

Return to “ECWolf”