Hello, this is an issue I’ve been suffering from lately that has been driving me nuts, and I don’t know why it’s happening or how to fix it.
So the game I’m working on has a grappling system, and previously it only worked with pre-built grapple point BPs that I had made. These BPs had a widget component with an arrow on it that would help visualize the player’s grapple trajectory. The code for the grapple point widgets basically looked like this.
However, as the game progressed we needed to be able to grapple to other things like enemies, so I moved the code that would make something “grapple-able” from the grapple point BPs to a component that I could stick onto any BP.
However, I still want that widget aspect of it to also apply to the other BPs, so I figured I’d make a child class of the default Widget Component and add both the grappleable code from the component mentioned earlier as well as the widget code from the original grapple point BP, basically consolidating the two into a single thing that does both. However, for some reason, I believe this happens after running the game with one of these new widget component children in the level, the BP for it just breaks and stops appearing. Like it’s still in the hierarchy of it’s parent but it is completely invisible. I believe it’s corrupting since I can’t do anything to make it appear again, even undoing things. Reloading the asset doesn’t help and often breaks the references to it from other blueprints such as the player. Here’s an example of what it looks like compared to the original, normal widget component in my grapple point BP.
If you have any ideas as to why this is happening and how to fix it, or an alternative way to achieve what I’m trying to do, PLEASE let me know, I have searched all over for help with this and I’ve come up empty-handed. Additionally, if you want me to further clarify something, again, let me know, I have a hard time explaining these kinds of complex scenarios.
Edit: I have found that just getting a reference to the widget component child doesn’t break it, as I can do that with another widget component child class just fine.