wildweasel

The feature that you're after is a Titlemap: https://zdoom.org/wiki/TITLEMAP

With Dehacked, the sound a weapon makes is tied to the code pointer that is used for the weapon's attack. Unfortunately, the Pistol attack and the Chaingun attack are both hardwired to DSPISTOL, and there is no easy way to change the sound of one without affecting the other. I can certainly think of a couple of Seriously Hacky ways to do it, but they come with very noticeable side effects; the safest would be to simply replace DSPISTOL with a copy of DSSHOTGN, though this would also affect zombies.

Another potential thing to look at: ensure that the player's StartItems include ammo for the weapon.

Just to make sure, are all those sprites present (in the correct place) in your wad file? If they are missing or not located in the right subfolder/markers, the actor doesn't appear.

That'd be the problem; the versions of GZDoom that used FMOD aren't compatible with FMOD Studio and need a specific older version of FMOD Ex. For whatever reason, the FMOD people didn't make Studio backwards-compatible. I don't know which specific version of FMOD Ex you need to successfully compile, but this might be a decent place to start: https://zdoom.org/wiki/FMOD_Ex Or try compiling a newer version of GZDoom that supports OpenAL.

The question remains, who is going to put in the time to do that to literal thousands of files? They can't "just" be automatically generated as-is; someone would have to write the code to do that, too, and account for edge-cases that will undoubtedly come up when your data set is that large.

But...how is the player to decide which to play? Even GZDoom's episode menu can only take a certain number of entries before it starts going off screen, and that number is well below the "thousands" of maps on these discs.

Unfortunately, The Golden Souls and its sequel make non-trivial changes to Doom actors and behaviors, making Brutal Doom incompatible with it. You could certainly still try, but it would have unpredictable results and may potentially make the game unplayable.

Update for those that care: I got the toolchain installed, along with what I assume are all its dependencies, but upon trying to Make in the 64doom/src folder, I'm running into problems where it's failing to #include libdragon.h and I don't understand how to tell it where to look for it. I even copied the libdragon files into (a copy of) the /src folder, no effect. I'll take a break from this for the time being - if I pick it up again, I'll probably go start a thread in Source Ports to avoid cluttering this one too much. (unless someone else feels like trying).

Favorite: Julius. A true "veteran" who never got a (canonical) game of his own, the best part of Julius is that he factors so heavily into the "bad" endings of the Sorrow games - and in Dawn, the bad ending is effectively its own remixed game. Sure, we know next to nothing about him as a person (besides him being a Belmont, and being irritatingly protective)...and we never did get that "war of 1999" game...but one can't deny, a Belmont with facial hair (and a kickin' trench coat) is pretty awesome. Least Favorite: Brauner. He's a cool boss fight, but he's totally wasted potential, because no sooner do you meet him, than he's unceremoniously booted out of the storyline in favor of Dracula, as if to say, "Fie to this pretender, there is room for only one Lord of the Night in this series!" (edit: weasel lives up to his member title yet again)

Well, given 64doom's maintainer never wrote compiling instructions (only instructions to build the ROM), this is gonna be an adventure...and it starts with installing the N64 toolchain. Here we go... 😖

I was going to say "Challenge accepted!", since I have an Everdrive 64 and all, but then I realized 64doom doesn't have a way to accept DEH patches or embed external files, unless I've missed something. I could merge D64D2.WAD into DOOM2.WAD, but that DEH does more than just rename maps, and I get the feeling the game would be pretty significantly broken without it...

The difference between them is that -file works exactly as -file did in vanilla Doom, where loading PWADs with changed sprites (or flats?) would throw out all sprites/flats present in the IWAD and use the ones in the PWAD instead - many older mods needed to include every single unchanged sprite/flat from DOOM.WAD for that to work correctly, which was illegal (you may see a lot of 1994/1995 WADs on /idgames that are noted as "cleaned" versions, as a result). Tools like DEUSF and DMADDS were used later, to splice the unchanged sprites into a PWAD in order to then use it with -file; -merge mimics this behavior so that these tools are unnecessary. Disclaimer: I have not read the Doom Specs and may be referencing certain facts incorrectly or just plain getting things wrong.

I can't be the only one a bit disappointed that these are just trading cards and not an actual deck-of-52. (Has that ever existed in a Doom form?)