Skip to content
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

Open
OpenRift412 opened this issue Mar 16, 2023 · 7 comments
Open

[Suggestion] Crispy-Style Autoloading #581

OpenRift412 opened this issue Mar 16, 2023 · 7 comments

Comments

@OpenRift412
Copy link

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.

@Altazimuth
Copy link
Member

A link to Crispy Doom's documentation for this feature or what have you would be appreciated. More details in general would be nice.

@OpenRift412
Copy link
Author

OpenRift412 commented Mar 16, 2023

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.

@Altazimuth
Copy link
Member

Where are these autoload folders located?

@OpenRift412
Copy link
Author

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.

@daemonspudguy
Copy link

@Altazimuth on Linux the autoload folders are in the config folder, by default .local/share/crispy-doom/autoload

@Meerschweinmann
Copy link

Meerschweinmann commented Sep 6, 2024

Where are these autoload folders located?

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".
These folders will be created in the "autoload" folder when a WAD is loaded. That is the same for PWADs.

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.

@Meerschweinmann
Copy link

Meerschweinmann commented Sep 6, 2024

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.
So whatever is loaded with "-file" is higher priority.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants