What are you trying to do here? Because you have a couple different problems going on.
First, the custom structure parameters should be F-type or int32 references. Searches through the engine don’t show any examples of UObject pointer types being used. Either the FType is a base type (like with data table APIs) or it’s a placeholder like the Array API’s.
Second, I suspect that this doesn’t work with multiple wildcards for some reason. The only example I could find of the engine specifying two parameters is in UFieldNotificationLibrary with int32&'s where both parameters would end up being the same type.
This is probably a similar limitation to how blueprint macros are implemented where they only recognize one wildcard type. If you try to make one with two, they will always become the same thing. If you want a node with multiple, independent, wildcards you probably have to go all the way to making a full K2Node in C++.
You don’t mention what version of the engine you’re on, but I should also call out that U-versions of reflection data are basically deprecated and have been replaced with F-versions. I’m not sure why they’re still around and not marked as such.
Yes I normally would use int32, and I did at first but it didn’t work. But I saw some others use UProperty types as a param for wildcard pins, so I figured I’d give it a shot. And yes I am aware that UProperties are deprecated for FProperty, however it would not compile when used as a parameter type.
I went take a look, and I noticed they didn’t use a space between the comma and the following property name (“A,B” instead of “A, B”)
So I tried it and sure enough it worked. Thanks for the help
