Disabling certain files in autoload?

[RyeFyre]

When you have a bunch of mods in the autoload config, you come across issues with more "full-featured" megawads and TC's that conflict with them.

One example is I use Target Spy for a generic health bar for enemies, but some mods already have their own health bar system built-in. Or Full Screen HUDS messing up when a mod already has a custom HUD.

Ultimately I don't want to mess with the config file every time I want to not load one or two files. My only guess is if there's a command-line argument that allows me to exclude certain files from the autoload, without disabling autoload outright. I usually use ZDL for my mod loading.

Hopefully someone can help out here. Thanks!

[Rachael]

The best thing to do in this case is to simply use an alternate config file. It might not be an ideal solution but it's the one that's closest to making things more convenient for you in your use case, right now.

You can also try and use an autoexec.cfg that can test for cvars, but not sure if that will work.

i.e.

Code: Select all

test <cvar> <value> pullin <file.pk3>

(without <>'s)

[Enjay]

Another thing that you might find useful is to not have the files that are likely to cause a problem on autoload, but keep them in the ZDL external files panel. If you have the right version of ZDL, files can be enabled/disabled at the click of a button.



In the above shot, NJ_PSXTra.pk3 and gearbox-v0.7.0.pk3 will not load but Test01.wad will. The little up arrow beside the + and - buttons toggles whether they will load or not.

[RyeFyre]

Huh, I didn't know that ZDL had that feature (I am running the same version). Just did some tests and it did just the trick for the mods in question.

Thanks for the help!