ZDoom

For reference, the engine knows which sound to use because each superclass of item has its Inventory.PickupSound property set to the appropriate sound name, and the individual item types inherit that. If you ever need to give a specific item its own unique pickup sound, you can toss that into the ...

ZDoom was one of the first Doom ports to include Hexen support, actually, and outside of a handful of multiplayer ports, its descendants have all inherited it. In fact, for a pretty long time, the only real options for playing Hexen were ZDoom, Doomsday, and ... just vanilla. As far as Hexen weapon ...

You have a state at the end that lasts 7 tics and uses the TNT1 sprite, which is blank, with no real sign that that wand is supposed to be off-screen or something similar. It's the one that calls A_TakeInventory to remove the SpecialAttackAxe token.

I'd personally not bother with the idea of a DeHackEd weapon mod, because the concept only really made sense back when it was the only option. Nowadays, though, the venn diagram of people who like to play with weapon mods and the people who stick to vanilla-to-Boom-compat ports is ... not one. I ...

there is something deeply distressing about the fact that zscript would flunk out of high school due to being unable to calculate the circumference of a circle

If there's a bug, it's that the function can make a sound at all. Cacodemons are the one enemy type that don't make a sound at melee range, so the fact that you can define one for it using AttackSound is wholly a ZDoom extension. Or an oversight.

A_HeadAttack is accessible to all actors by default to begin with. That's why the Cacodemon definition extends the function to Actor to begin with, instead of just defining it for itself - it's effectively just a way to organize things by having functions related to a particular actor be defined ...

Do other properties break when put in this specific defaultmap?

Because if this is in a separate MAPINFO than the actual map definitions, I could imagine this being a load order thing where this defaultmap entry is being processed after all the map entries.

Should be noted that using this method means that a player can shoot a mid-range rocket, then switch to the chainsaw before the rocket lands and have the monster blow up into ammo confetti. Relying on the player's currently equipped weapon for this kind of thing is only really feasible when every ...

Actually, it was more about how incredibly tough they are. They have the health of a lost soul and basically the same pain chance as a pinky ( 62.5% vs 70.3% ), but with twice the flinch duration. The chaingun chews through them like nothing. The only thing keeping 'em from being like wet paper is ...

There's the DeathType property if you want to do it per-projectile, at least.

You might also want to check for bVULNERABLE. It's a pretty infrequent flag, but it nonetheless allows an non-SHOOTABLE actor to be damaged by splash damage.

It's because HexenArmor with a non-0 amount acts as Dragonskin Bracers. All normal HexenArmor pickups give 0 of themselves to avoid this. Also, it goes without saying that your solution to this makes it so that already having those particular pieces of armor means you don't get +5 AC, but a lesser ...

From the look of it, you're trying to apply a lower texture to a one-sided line. That's not really how they work - a lower texture is only applied to the edge of a higher floor, so a one-sided line won't ever show a lower texture because there's nothing for it to apply it to. There's a trick you can ...

Nope. Hitscan and melee attacks don't use properties at all. That said, it is only projectiles, bullet attacks, and ( player ) melee attacks that have damage randomization by default. Railguns, radius damage, etc. all do static damage unless you set them otherwise ... though if you just shove a ...