Skip to content

Added NotifyMatchType to OnNotifyFromActor - #391

Open
fede-Raider wants to merge 6 commits into
MothCocoon:5.xfrom
fede-Raider:5.x
Open

Added NotifyMatchType to OnNotifyFromActor#391
fede-Raider wants to merge 6 commits into
MothCocoon:5.xfrom
fede-Raider:5.x

Conversation

@fede-Raider

Copy link
Copy Markdown
Contributor

Summary

Adds a new NotifyMatchType (EFlowTagMatchType) property to UFlowNode_OnNotifyFromActor, letting users choose how the NotifyTag should be matched.

Motivation

Previously, OnNotifyFromComponent matched NotifyTags using NotifyTags.HasTagExact(Tag), which only accepted exact tag matches.
This made it impossible to set up a node listening for a parent tag (e.g. Notify.Interaction) that should trigger on any of its children (e.g. Notify.Interaction.Pickup, Notify.Interaction.Use).

Changes

  • Introduced EFlowTagMatchType type.
  • Added EFlowTagMatchType NotifyMatchType property to UFlowNode_OnNotifyFromActor.
  • Replaced NotifyTags.HasTagExact(Tag) with FlowTypes::HasMatchingTag(Tag, NotifyTags, NotifyMatchType), mirroring the existing pattern already used for IdentityMatchType.

Testing

  • Verified exact-match behavior is unchanged when NotifyMatchType is set to HasExact (default value).
  • Verified parent tag now correctly matches child tags when NotifyMatchType is set to Has.

UFlowNode_ComponentObserver: fix SuccessCount persistence on save during Success flow
Introduced a EFlowTagMatchType, replacing the hardcoded exact-match check with a configurable one.

This allows the node to listen for a parent Notify Tag and match against any of its child tags, instead of requiring an exact tag match.
EFlowTagMatchType::HasExact as Default value of NotifyMatchType
}

if (IdentityMatches && (!NotifyTags.IsValid() || NotifyTags.HasTagExact(Tag)))
const bool IdentityMatches = FlowTypes::HasMatchingTags(Component->IdentityTags, IdentityTags, IdentityMatchType);

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use of already existing utility function

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant