Changing component name in one blueprint changes the event component variable in another opened blueprint

I have several blueprints open, one is a character and the other is for a projectile. As I was creating components and overlap events I stuck with the default names. I had a collision sphere on both my character and projectile called “Sphere”. I had an event, OnComponentBeginOverlap, on my projectile referencing Sphere. I changed the name of the collision sphere on my character to “DamageArea” and the OnComponentBeginOverlap(Sphere) on my projectile changed to OnComponentBeginOverlap(DamageArea). The Sphere in my projectile was still Sphere. If I changed the name in my projectile to DamageArea and then go back into my character and changed DamageArea to “Whatever” it would change on the OnComponentBeginOverlap.

Hello ,

I was unable to reproduce this issue on our end with the information provided. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. What version of the engine are you using?
  2. Can you reproduce this issue in a clean project?
  3. If so, could you provide a detailed list of steps to reproduce this issue on our end?
  4. Could you provide screen shots that are more close up of the blueprints involved?

UE version is 4.7.5… Event did not happen in a clean project.

Hello ,

Can you provide any additional information that could help us reproduce this issue on our end? Was this project one that was updated from an older version of the engine?

Hello ,

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 offer further assistance.

Thank you.

I have encountered this issue as well, in 4.7.6. My character blueprint contained a box collision component named the default ‘Box’. Another blueprint, which contains a cast to my character blueprint, also contained a default ‘Box’ component. Both blue prints contain the ‘OnBeginOverlap’ and ‘OnEndOverlap’ events. Upon changing the name of my characters ‘Box’ component, the other blueprint’s Overlap events changed to match the new name in the character blueprint. The collision component stayed with the default name in the non character blueprint. The overlap events did not fire until I removed them, and added new overlap events from the right click menu of the non characters collision component. I was able to add these new events without deleting the affected events, ctrl dragging the wires to the new ones. I have been unable to reproduce this error in mine, or a clean project.

Hello Noeticized,

I have tried to reproduce this issue on our end with the new information provided in your post, however I was unable to reproduce this issue on our end. Are you still experiencing this issue on your end?

I’ve had this problem several times and was able to reproduce this. Just did this in the Memory game example. What I did was:

– add box collision on BP_MenuMem and set the name to BackToMenuButton
–compile
–change the name of BackToMenuButton that I just created
–compile

Then if you look at the BP_ScoreBoard the events for BackToMenuButton changed to whatever name was changed on the other blueprint and they no longer function.

Hello rckt26,

Could you tell me what version of the engine it was that you reproduced this issue in?

latest version - 4.8.3

Hello rckt26,

I downloaded the 4.8 version of the Memory Game and could not reproduce this issue with the information provided. Were there any small steps that may have been left out?

I just created a new project for the Memory Game and here are some screenshots of what I did to get the error. Starting in pic 2 in BP_MenuMem blueprint I create a box collision with name BackToMenuButton and then compile. pic 3: I then change it to Box and compile. pic 4: then looking over at the BP_ScoreBoard blueprint you can see the events changed from what they were in pic 1.

Hello rckt26,

I was able to reproduce this issue on our end. I have written up a report ( UE-20325) and I have submitted it to the developers for further consideration. I will provide updates with any pertinent information as it becomes available. Thank you for your time and information.

Make it a great day