Binding to the event from the StaticSlot instead of my slot instance is what I did as a workaround - and it does the job. I marked this as a hack in the code base, because I wasn’t sure if that’s a safe solution. Looks ugly, that’s for sure. I might try using Serializable Interface, thanks for the suggestion.
But that’s a fix for my C++ code, and Savior’s blueprint node mentioned in my previous post is still broken. Do you plan to introduce similar workaround to the node’s code?