ProcHitReact addresses all these common limitations:

• Supports multiple overlapping hit reactions
  • Repeated hit reacts are handled seamlessly without snapping
  • Child bone blend weights are not overwritten by parent bones
  • Seamlessly blends differing profiles and parameters
• Option to disable blend weights or physics sim on individual bones
  • Supports holding weapons
• Consideration for real-world application in complex projects

In many cases, all it takes is putting a component on your character, assigning profiles, and calling HitReact() on it.

When setting up something out of the ordinary further setup is necessary, but it can be done even in blueprint.

Supports Linear, Angular, and Radial impulses.

Supports disabling physics or using custom blend weights on child bones of the simulated bone.

This means we can disable physics only on the arms for our character who is aiming a rifle!

Blacklist bones that don't simulate well, such as the pelvis which can cause the entire mesh to simulate!

Supports extendable data-asset profiles, simply specify the profile you want to use when triggering a Hit React.

The included HitReact component has many profiles setup for you out of the box with tested defaults.

You can toggle the entire system on and off, with or without interpolation.

If you have the Gameplay Abilities (GAS) plugin enabled in your project, you can use tags to enable and disable the system. This is an optional dependency, ProcHitReact does not require that your project uses GAS and will not enable it for you.

The system automatically stops itself from ticking when it doesn't need to.

Featuring a purpose-built interpolation framework, you can customize the blending to your liking.

The available states are: Blend In, Hold, and Blend Out. Hold will maintain your physics at max blend weight for the duration.

Reapplication can be throttled by setting a Cooldown.

Physics bodies have custom simulation behaviour, nothing so primitive as using SetAllBodiesBelowPhysicsBlendWeight()

Generally hit reacts are entirely cosmetic and should be applied via gameplay cues or other generalized multicast/replication events.

The data types used by ProcHitReact, including the application parameters, are net serialized for you, so you can replicate these too.

Dedicated servers don't process hit reacts, unless you enable the setting.

ProcHitReact was designed with multiplayer games in mind.

See the debugging section on the Wiki to learn how to Debug ProcHitReact.

• Initial Release