Discord Support: https://discord.gg/FrBMHSJGkM
This is a lightweight component, it simplifies the Montage RPC process and use events to handle Montage's logic
In the example, includes weapon switching & attack & combo & hitreact & weapon trails & weapon hit trace
OwningClient: montage will be played on the OwningClient first, then played on Server, and finally Multicast to other Clients
For example, you played a 1-second Montage (NetworkPriority=OwningClient), and another client network delay is 0.5-second. this client will saw your montage is played starting from 0.5. This will ensure that other clients are at the same progress as your montage
I prefer to handle Notify in Actor instead of creating BP_Notify files because in Actor can easily modify values and change resource files at runtime.
In the example. I created a BP_Weapon that handles Combo & Weapon Trails & HitTrace notifies, and then used Child Class to change Trails FX. I think this way is more flexible and clean. This is just optional, you can also use BP_Notify if you want
Then handle Notifys through the component's Events. This way, all the logic of the Montage can be kept in one BP_Actor
There is a useful function NotifyStartsWith? in the component. It's used to split NotifyName and allowing you to simply handle complex Notify
