In case you change a variable type from one class ref to another class ref blueprint pin connections working on this class ref variable.
This will lead to silent bugs which are not catched by the blueprint compiler.
Those disconnected bugs are hard to detect.
The expected behavior would be to not break pins and instead issue compiler errors which have to be fixed.
If you change a variable type to a non compatible one it will break because it can’t connect in the first place.
I know this and this is exactly the point. It should simply not break and instead issue compiler errors
You get a compile error where the pins are broken though.
This is not true in any case. It would only be true for reference pins. And another disadvantage is that you have to figure out on your own which pins broke and what is the output->input relation.
I was not able to reproduce your issue on our end. I have a couple of questions that will help me narrow down the issue you are experiencing.
- Can you reproduce this issue in a new project?
- If so, could you a provide a detailed list of steps so I can reproduce this issue on our end?
- Could you provide screenshots of the issue you are experiencing?
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.