ZDoom

While I understand Rachael's reservations for cluttering up the code, this is simple enough to not become an obstacle like the infamous pain flags.

The scope of that function is too narrow.

ClearInventory would need to be applied to other actors when they might not even exist in the mod, or some actors that are incapable of inheriting from another.

Furthermore, stacking on check after check for actor classes/names costs more than an extra check for a flag.

But clear inventory is virtual, so you can override it with you own function.
https://github.com/coelckers/gzdoom/blo ... y.txt#L314
Or you talking about acs clear inventory function?

Also, yes, "exception to the exception for the exception" is not good. Since at some moment function would contain only exception for the exceptions, with handling for the exceptions which doesnt except exceptions from the previous exceptions list.

Adding onto what Phantom said, I would have to create hacky workarounds that make it even MORE unwieldy than introducing an Unclearable flag, JUST so I can clear the Undroppable flag and then drop an item.

An upcoming mod of mine is reliant upon ensuring inter-mod compatibility will work properly, since you can have multiple players at once.

In this case, there's a real use case for the feature: depending on what you're doing with your mod (an RPG mod, for example), ClearInventory can actually completely break the mod - I imagine this would be for situations like that.

In the wake of what seems to be yet another trend of creating yet another massive pile of very light-weight convenience features - why do you need this?

I'll be honest - the reason why I don't like this is because ClearInventry() in my opinion should do exactly what it implies - the need for exceptions for every little thing in the game engine is senseless to me - which often evolves into exceptions to exceptions - and the DamageMobj refactor should stand as a perfect testament to that.

Piling on exception to the exception after exception to the exception after 50 dozen more exceptions is exactly what gets the engine into such an unwieldy state in the long run.

Graf has merged this PR so this can be closed.

Pull Request
I'd like to allow items to remain droppable at any time, yet immune to ClearInventory.