-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Suggestion] Crispy-Style Autoloading #581
Comments
A link to Crispy Doom's documentation for this feature or what have you would be appreciated. More details in general would be nice. |
Essentially Crispy Doom has an autoload folder and in that folder you would have a folder named after a respective IWAD or PWAD (i.e. a folder labelled doom.wad). You could then put WADs inside those folders and they would load automatically on launch when you ran the engine with the respectively named IWAD/PWAD. Woof, PrBoom-plusUMAPINFO, and DSDA-Doom have this feature as well. |
Where are these autoload folders located? |
It's configurable. Though I think the best way it can be implemented is to have it be a subfolder next to the main EXE. |
@Altazimuth on Linux the autoload folders are in the config folder, by default .local/share/crispy-doom/autoload |
Here is an articel from chocolate-doom. https://www.chocolate-doom.org/wiki/index.php/Autoloading For Windows it is normally an folder named "autoload" in the folder the sourceport is installed. In the autoload folder are subfolders named by the WADs inclusive file extension you have loaded. For DOOM this folder is named "doom.wad", for Heretic "heretic.wad" and for DOOM2 "doom2.wad". And there is a special subfolder in "autoload" called "doom-all". That handles mods that should be used for all DOOM games. "Smooth-Eternity" mod or "Vanilla smooth weapons" mod could be such a candidate. I am not sure If the autoload folder is handled to be loaded before or after the -file loaded WADs, but i could test this later. |
Had tested with Crispy DOOM, International DOOM and Woof. The files in the autoload folder are loaded before "-file" loaded WADs. For example, if someone has alternative DOOM music or widescreen assets in the "autoload" folders they do not "overwrite" the music or graphics of a loaded PWAD that has different music and/or TITLEPIC/intermission screen. |
Is there any chance we could have an autoloading feature structured similarly to how it is in Crispy Doom? This would be a lot more helpful for stuff like widescreen assets for WADs. Plus it would be a lot more useful than the current method of autoloading.
The text was updated successfully, but these errors were encountered: