Add link event trigger node. - #449
Merged
Merged
Conversation
Hoikas
force-pushed
the
link_event_trigger
branch
3 times, most recently
from
December 14, 2025 23:01
0dc2b48 to
c69c4e4
Compare
Hoikas
force-pushed
the
link_event_trigger
branch
from
June 18, 2026 02:26
c69c4e4 to
89d0fa5
Compare
Hoikas
force-pushed
the
link_event_trigger
branch
4 times, most recently
from
July 4, 2026 17:08
843c32c to
8fa9f55
Compare
Hoikas
force-pushed
the
link_event_trigger
branch
3 times, most recently
from
July 15, 2026 21:26
5e38c20 to
8e57cbb
Compare
These are annoying to create by hand, so put the details behind a friendly method.
This node is a high level wrapper over the xLinkEventTrigger Python script I wrote to fire off a Responder on link-in or link-out. It uses plActivatorActivatorConditionalObject to be able to trigger anything attached to a logicmod.
While it was great that I finally found a use for `plActivatorActivatorConditionalObject`, the problem with it is that it doesn't forward any of the event data records from the triggering notification. That means if you want to have a tree that acts on a specific player, that information would be lost. So, I'm going to limit this to just triggering responders for now. Maybe someday, we'll modify all engine versions that are pertinent to forward the event records correctly.
Hoikas
force-pushed
the
link_event_trigger
branch
from
July 15, 2026 22:09
8e57cbb to
117203d
Compare
Member
Author
|
This is now ready for feedback. I will only leave this PR up for feedback for ~24 more hours. 
This node is a high level wrapper around xLinkEventTrigger.py and allows firing off an arbitrary responder or basic responder. I removed the whole activator activator thunk thing because I learned that activator activators do NOT forward event data, so information about which avatar did the trigger is lost. That means you cannot play animations on specific avatars. Additionally, I have decided to remove the other high level logic nodes from this PR because they do not relate to this particular node, and none of them use the thunk method I was tinkering with. |
Deledrius
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a higher level use case of the xLinkEventTrigger.py file introduced in H-uru/Plasma#1821. RIght now, this is just an example. I still have some iteration to do here, and I would like to add some more high level logic nodes to improve the workflow where Python has to get involved.
Python File nodes are tricky because the attributes are inputs to the script but function logically as outputs. For example, responders appear as an input to a Python file node, but Python file nodes can trigger responders. The inverse is also true. In the case of
xLinkEventTrigger.py, we see the same thing - normally an activator is an input/trigger for a Python file node, but, in this case, the Python script is triggering the activator so that the responder or other things connected under "satisfies" can proceed.