by Caligari87 » Thu May 11, 2017 9:25 am
Please no tons of little files, that's just messy. It also would be a nightmare on Linux since package management dictates program binaries, data, and configuration are split up across the filesystem. I hate diving into /usr/games/doom or /opt because it requires root, but if you put them in ~/.config/gzdoom then the metadata is detached from the files it refers to, which is just gnarly IMO..
My other fear is that if you add in some kind of externalized "automatic" any-IWAD recognition, a ton of people are going to start abusing it and making their mods "IWAD" just so they'll show up in the box, just like the skins folder was abused. Perhaps this is an irrational fear, so maybe talk me down a little, but I don't see it ending up anywhere good.
To me, any IWAD of sufficient note can be added to the internal list by popular consensus, such as we're discussing here. That should be more than sufficient. For everything else there's -iwad and/or gzdoom.ini.
...
Perhaps a "compromise" would be to have a cvar or .ini option that says "treat any wad/pk3 in the IWAD search paths as an IWAD"? Opt-in obviously, so it puts the onus on those who organize their mods accordingly.
Please no tons of little files, that's just messy. It also would be a nightmare on Linux since package management dictates program binaries, data, and configuration are split up across the filesystem. I hate diving into /usr/games/doom or /opt because it requires root, but if you put them in ~/.config/gzdoom then the metadata is detached from the files it refers to, which is just gnarly IMO..
My other fear is that if you add in some kind of externalized "automatic" any-IWAD recognition, a ton of people are going to start abusing it and making their mods "IWAD" just so they'll show up in the box, just like the skins folder was abused. Perhaps this is an irrational fear, so maybe talk me down a little, but I don't see it ending up anywhere good.
To me, any IWAD of sufficient note can be added to the internal list by popular consensus, such as we're discussing here. That should be more than sufficient. For everything else there's -iwad and/or gzdoom.ini.
...
Perhaps a "compromise" would be to have a cvar or .ini option that says "treat any wad/pk3 in the IWAD search paths as an IWAD"? Opt-in obviously, so it puts the onus on those who organize their mods accordingly.
8-)