Comments - terminator44

I noticed shotguns dropped by shotgun guys seem to give 8 shells in Purist mode and 2 shells in the other modes, as opposed to 4 shells in vanilla Doom. Also, boxes of rockets now give 3 rockets in all modes, instead of 5. Were these changes intentional?

Just tested it with 3.0.0 and it does work. Thanks for the update.

Isn't this the version where the janitor can't be turned off? Yeah...no thanks.

I could understand the BHG, but I don't like the idea of adding a different ammunition type for the BFG. That's been done in the Mutators and it often results in finding only one type of ammunition and not having any to use the other group of weapons. Pistol/rifle rounds and grenades/rockets cause enough issues for map balance already, but at least the weapons in those are similar enough that they are interchangable. That's not really the case for the Slot 6, 7, and 8 weapons, which are fairly distinct from each other.

I've used several HUD mods for Doom, and this one is by far the best! Keep up the good work, Hexereticdoom.

In addition to what everyone else has said, if you're using UDV as your HUD you may want to switch it for another HUD, as UDV is incredibly resource intensive. I personally recommend HXRTC 7.0. It has all the information you need in a clean, easily readable format and is much lighter than UDV: Moddb.com

Remember when I posted the bug about Hellknight/Spidermastermind infighting causing the game to crash? Well, that bug has been fixed, but it seems the two monsters still cause problems. This time the game crashes whenever the Spidermastermind, Hellknight, and Baron of Hell are in the same room and begin infighting. No two of these monsters causes the issue, and I'm not sure what specific behavior causes the crash, but I can repeat the crash fairly consistently by putting these three in the same area.

Just like before, I am using Project Brutality 2.03a and GZDoom 2.1.1.0 x64 (64-bit). I am running Windows 7 Professional 64-bit with an Intel Core-i5-3570K CPU and a Nividia GTX 970 GPU.

My load order is as follows:
Project Brutality 2.03.pk3
UDV_v1.62_A_BASE_GZDoomOnly.pk3
UDV_v1.62_B_ADD_IN_Mod_ProjectBrutality.pk3
PB_Allow_SV_Cheats.pk3

I am not using ANY compatibility patches and in fact have deleted them as I have no intention of using them.

On that note, does anyone know the GZDoom console command to kill all Spidermasterminds in a level in PB? I've never particularly liked that enemy even in original Doom and it would be a good temporary fix until the bug is found and corrected. "Kill Spidermastermind" doesn't work, so I'm guessing it is referred to as something else in PB?

You're the best, pa1nki113r!

Yeah. The first few times the crash happened I figured it was an memory overflow error from large numbers of enemies or large numbers of shell casings left behind by the Masterminds, since it usually happened on slaughter maps. Then it happened on a small map with few enemies but 4 Masterminds, and always at the same time: when a group of Hellknights teleported in. I tested MAP20 in Doom II and sure enough, I was able to pin down the source. You can test yourself by finding a map with a Mastermind and typing "Summon Hellknight" into the console and see the results.

I've encountered an unusual bug. Whenever a Spider Mastermind attacks a Hellknight, whether intentionally or not, the game crashes. This consistently happens with the base Hellknight (the Cyber Hellknight and Paladin do not cause this effect) and the base Spider Mastermind or the Demolisher variant (the Juggernaut does not cause this effect).

I am using Project Brutality 2.03a and GZDoom 2.1.1.0 x64 (64-bit). I am running Windows 7 Professional 64-bit with an Intel Core-i5-3570K CPU and a Nividia GTX 970 GPU.

My load order is as follows:
Project Brutality 2.03.pk3
UDV_v1.62_A_BASE_GZDoomOnly.pk3
UDV_v1.62_B_ADD_IN_Mod_ProjectBrutality.pk3
PB_Allow_SV_Cheats.pk3

I am not using ANY compatibility patches and in fact have deleted them as I have no intention of using them.