Hello,
I’ve come across a problem where a custom event bound to an event dispatcher that passes a parameter will be broken when the project is loaded if the parameter of the dispatcher and the custom event don’t have the same name.
When first created the blueprint will compile and run without problem, only when you save an re-load the will the error occur.
It seems like it’s renaming the parameter on the custom event to match the event dispatcher when you load the project.
Reproduction steps:
- Make a new blueprint
- In the blueprint create a new event dispatcher and add an input parameter
- Create a new custom event and add an input parameter with a matching type to the dispatcher parameter but with a different name.
- Bind the event dispatcher to the custom event.
- Link the parameter of the custom event to something e.g. a print string. It should compile without errors.
- Save and re-load the project. The blueprint should now show an error with the custom event.
Expected result:
Either there should be an error in the first place, or it should allow different names as long as the type is the same.
