/vr/ - Retro Games

>>4356805
Stunlock in later FPS games is probably handled more effectively anyway. These are demons we're talking about here, pain is their pleasure, or something.

Id expect stunlock to be a Damage Amount type of deal rather than how many times you get hit with something. It was always rather upsetting that an Archvile could take a rocket to the face and not flinch, but yet the shotgun had any chance at all to do so.
> the only thing in doom that id expect could take a rocket and have any chance of not flinching are bosses, including the baron, but on the low end for the baron
> even just because thats Alot Of Force to be hit with that could literally knock a demon on its ass even if it didnt care about the pain

There was someone who was working on, or managed to make a non-random counter based pain system, dunno where it is now.

Im not saying stunlock is a bad thing or the capability to inflict flinch states, the lack of it or use of it can be abused by a designer either way. This is one of the benefits of using damage types so that you can give stunlock as a benefit.

> Chaingun Stunlock
I thought of a cute way to deal with this while still keeping it mildly pleasing to use. Give it its own damage type and allow monsters to still get stunned at the usual rate.

Except make the painstate for that damage type only generate a full painstate on a lower random chance. So that it only freezes them for 1 or 2 tics - meanwhile if they were in the middle of an attack you give them a boolean counter (depending on how far into the attack animation they were) and if they still have that counter at the end of the painstate they instead jump straight back to the attack
> so that they arent actually stunlocked even though they're showing that they were damaged, it doesnt let you off the hook of being shot/scratched/scorched

Same dynamics can be applied to other things. I particularly like the idea for Cyber since he can show you his lack of amusement, but not stop his attack

>>4100430