ZDoom

I think a hard limit is out of the question because it becomes impossible to know what a "safe" amount of textures is. One thing I haven't seen mentioned at all is the idea that multiple mods could be allocating textures for similar purposes. Assuming we have a tiny 1gb pool, this means mod A might ...

There was a bug where bad visual thinkers were getting into the render list after loading from a save which would also affect hubs. Not sure if it's relevant but just spitballing.

My solution for this in my mods is to usually just save the velocity and reapply it after kickback is calculated when damaged, however I'm not against just adding an Actor flag for this because it would allow others to easily fix this in things like their Doom mods as well. As for the velocity check ...

Looks like quick saves are instant unlike any other form of saving/loading in the engine. This means it's now saving out the player's predicted state which causes it to crash when it loads back in because none of the prediction data is saved out. Edit: Yeah, quick save rotator was completely broken ...

Pretty neat little mod; however, that save deletion feature caught our attention. Unfortunately we're going to have to lock that down because while we understand some restraint was shown here, it's clear this is a path for someone to do something much more asshole-ish (this also didn't work unless ...

Does this mod use visual thinkers by chance? There was an oversight where destroyed ones were getting into the render list on load including from snapshots. It's possible it could've been this since the conditions for it were fairly random

Have hopefully found a fix for this. For some reason on load garbage visual thinkers kept finding their way into the render list.

Realistically I think the easiest way to track this down is gonna just be hooking the debugger up to a Debug build and playing until it freezes. This is probably too difficult to find by eyeballing without shear luck playing a part

Are you using the version of Project Brutality bundled with your mod or the latest build? If using the latest, it wouldn't hurt to test it with the bundled one to rule out a possible bug that got introduced by the mod itself

Can you confirm this map specifically is randomizing in vanilla Hexen? You're using map spots which, according to the teleport code, was an oversight on MAP10. You're supposed to be using teleport destinations for the randomized behavior. If this also works in Hexen then I'll update GZDoom to ...

I'm not sure why it aborts, but the logic is wrong here. You need to store snext before removing the Actor, otherwise the snext pointer will no longer valid by the time it sets it to the next one. It's possible something isn't getting cleaned up correctly which is why it's aborting since iirc it ...

What happens if you use "FFFF0000" as the argument? A lot of things in GZDoom ignore the alpha argument on colors so it's possible the alpha is getting actually used here.

Here are some of the highlights of this patch I personally think are worth pointing out: Innumerable amounts of fixes for bouncing projectiles. Not doing damage when bouncing off tops/bottoms of Actors, incorrectly bouncing off 3D floors, certain flags like THRUGHOST not working, incorrect bouncing ...

They should. Basically, when given the final assembled weapon instead of checking the exact defined weapon it'll now check if it has a valid replacement. This means if your custom weapon pieces were only there to give it a new replacement class type, they can be removed since the replaces on the ...

Seems some value is still getting mangled, though I'm not sure which (audio errors implies position related). I've noticed loading in general has some very odd properties when in multiplayer, however I wasn't able to actually get the above error you described in my testing. It could also be possible ...