ZDoom

ahh yes that might work. thank you

De-M-oN wrote: ↑Mon Dec 02, 2024 10:26 am But that would disable pain entirely.

Yes. You do not want to place it in a puff or projectile's default field, but rather randomize whether it is true at the puff or projectile's creation, as per the above post. Just replace bFORCEPAIN with bPAINLESS.

Professor Hastig wrote: ↑Thu Dec 05, 2024 5:37 am Aren't there enough questionable pain flags already? The code looks horrendously convoluted to handle all the special exceptions that were added to it.

Actually I agree. There's absolutely *WAY* too much override-of-override-of-override-of-override-of-override cruft in the Actor class as it is and this post reminded me of that.

Aren't there enough questionable pain flags already? The code looks horrendously convoluted to handle all the special exceptions that were added to it.

The flag can be applied randomly based on chance. In the case of puffs you can use inheritance and swap a painless puff out for another when you need a lower pain chance for the puff.

I know this is far from ideal, it's a bit hacky, but a proper implementation ("fix" if you prefer) for this will require a full flag anyway because it would require overriding behavior that would likely break old mods without it.

But that would disable pain entirely.

The PAINLESS flag on your puffs or projectiles can be used to achieve the opposite effect.

Is it also possible the opposite way?
So that I can have a faster chaingun, but the painchance stays same/similar?

Appreciate the help.

This is a "just" tier solution but here's how you can legally hack it:

I could really use a way to adjust pain chance on weapons, without the need to edit monsters. A setting like PainChanceFactor would work wonders. Currently, if I want a powerful weapon to have a higher chance of stunning, my only recourse is adding a bunch of mini a_explodes to the impact.