-noautoload disables HUD stats

[kitchen-ace]

I'm guessing that -noautoload disables all the autoload resources that come with Woof, but this means disabling some other features you might not want. Sometimes you need -noautoload to not conflict with wads that have custom resources, e.g. Pirate Doom 2 can crash if loaded with the Minor Sprite Fixing Project, wads that use custom Dehacked can conflict with casual play mods I normally autoload, and of course I want to disable autoload stuff when recording demos

Ideally I would love to be able to have different levels of autoload in the woof config dir, so that for example -noautoload 1 (or just -noautoload) disables only the things I've put in some directories that are likely to conflict with other wads, -noautoload 2 disables everything in the autoload woof dir, and -noautoload 3 disables even the Woof-provided resources.

edit: I'm on Linux and the Woof autoload resources are installed in their own directory, maybe that isn't the case with Windows though.

[liPillON]

This is related to another issue I've raised not that long ago, but I personally find the concept of different "autoload levels/thresholds" to be overkill.

I proposed a different approach in this comment:
#1648 (comment)

Basically the core-feature-enabling lumps (brightmaps, hud) should imho always be loaded, regardless of the -noautoload parameter and also for the shareware iwad (this has since been implemented).
Other ports do this by storing essential lumps in port-specific pwads (dsda-doom.wad, gzdoom.pk3, etc..)

[rfomin]

Other ports do this by storing essential lumps in port-specific pwads (dsda-doom.wad, gzdoom.pk3, etc..)

Yes, we are planning to do that.