ZDoom

Then we are done. I am not expecting to be coddled, but if all I am going to get is more accusations for everything I say, then what's the point? You want answers. You have one hell of a way to go about "getting" them, one that is tried and proven never to work. And then you expect me to break the ...

Let's see how it works out for the recipients of the award.

Damn, Skulltag 2: Electric Boogaloo is kinda fire ngl.

Check the filter settings.

This seems like an oversight rather than a deliberate decision. It gets really confusing with multiple secrets cause you don't know whether or not you've visited one before when both explored and unexplored secrets have the same color.

Not much to say here. Use case is better customization. Right now the only way seems to be slapping bCANTSEEK = true on stuff but that requires messing with the target actor, which can potentially cause conflicts if only specific seekers are not supposed to seek the target.

Saw the fix. I appreciate the quick work, man. Thank you.

Using the portable installation. Let's say I have a save file called Ace.zds. I am noticing the following problem: - If the save is in the root Save directory, "-loadgame Ace.zds" will look for it in Save/doom.id.doom2.commercial. Game launches but the console spits out "Could not read savegame ...

Yes please. This would be perfect for my use case and addresses the initial suggestion.

I see. In that case I can try what AFADoomer suggested. Thanks. I suppose this could be closed.

I mean something that DOESN'T count the color escapes. Both Length and CodePointCount are completely useless whenever I need to work with a colored string, which is 99% of the time. I tried using FIlter() out of frustration but that didn't do much either. Hell, anything that allows me to get rid of ...

I was afraid of that. Hopefully it's feasible down the line and not completely out of the question because refactoring DamageMobj seems like a good idea. A lot of calculations regarding damage are located in there so selectively modifying behaviour mod-side is a pain in the ass. Probably one of the ...

Following the train of thought here , the idea behind DMG_TEST (or DMG_NODAMAGE, whatever works) is to call Super.DamageMobj to get the final damage without doing any real health reduction. This way I can operate on the value after it's been modified by factors and whatnot, and use it in ...

Use case is allowing modders to reorder the calling of AbsorbDamage on items without overriding the entire DamageMobj virtual. I currently do this by building an ordered list of mod-specific items manually in the player's DamageMobj and calling Super.DamageMobj at the end with DMG_NO_ARMOR after ...

This can be closed, the PR has been merged and I can confirm it works fine. Thanks again to everyone involved.