9. Final Notes

• When creating a new widget for the HealthResourceWithUI component, you can create a function with the name SetResourceComponent using a ResourceComponentBase input and the function will automatically be called when using it as an Onscreen Widget or Overhead Widget.
• The HealthResourceWithUI component is not as malleable as the Health or base Resource component. It is primarily made to be a quick “drag and drop” on an actor blueprint.
• If these components are not functioning correctly in multiplayer, make sure the owning actor has Replicates enabled. If you’re using the components on a mesh you simply placed in the world it will not immediately work as that is not Replicated.
• The components above will work on actors and their subclasses. Keep in mind certain functionality such as onscreen functions will not work unless they are placed on a controllable Pawn or Character.
• All variables in the Details panel will be in either of these three categories: Resource, Health, UI. The functions in the function library are in: Resource Function Library.
• Some variables cannot be set with a simple **Set Variable **node, but must use the related setter function. This is due to other functionality being required when setting these variables to make sure the entire component updates correctly.
• Currently all modifications are stackable. Adding 2 “weak to fire (x2 damage)” modifications will result in x4 damage. Meaning there are NO precautions when accidentally adding duplicates. Additionally, removing modifications by that name will remove ALL modifications with that name, so you are not able to only remove 1. While this can be worked around, explicit functionality to better support this will come at a later date.
• Using a Modification with the Type of **Override Damage **will stop any further modifications and revert any previous modifications making the incoming damage be the magnitude value.