Hi!
So i’ve created an open door blueprint, had it working relatively fine but then when I either copy and paste another door, or drag another door blueprint in, the new one works, the old doesn’t. I presume its because the blueprint is casting to the door static mesh, therefore making the old one not work. I just cant seem to find the issue, UE5 noob here!
I will attach my blueprint and appreciate and advice given!
Hi there and welcome to the forum.
There are some serious design flaws here 
Most of this code should not be in your door actor. It is detecting the input always (well, last one added is…) doing a line trace when player is left clicking, presumably to see if the character is looking at ‘it’, but actually ‘working’ if character is looking at any door. If a door is hit by that trace, you cast it but then never use the result, instead adjusting self (the door that we are). Not that I am suggesting you should be using the cast door, that cast shouldn’t exist, just trying to highlight how confused this is.
The crux of your problem is that you enable input for doors on BeginPlay, and you can only have input enabled for one actor (per player), so the last one wins.
You need to move most of this code into the character (or controller), if the line trace hits a door, enable input for that door then. When the traces are no longer hitting that door, disable it. In the door actor remove the Begin Play, delete everything in the DragDoor handler after the IsHoldingLMB sets (that should all be in your character now) and I think you should be most of the way to a working system.
You have also got output from an impure cast in your DragDoor handler connecting to a node that is ultimately used in Tick. If you follow advice above you will get rid of that anyway, but don’t do this: if something has execution pins, only use its output in nodes on the same execution path. Pure functions and pure casts can be “shared” in this manner, those that go on the execution path explicitly can/should not. Your door (single) is working and you are not getting tons of “Tried to acces none…” after running it, so I guess it is ‘working’ and using the most recent value from when the cast last ran, which is far worse than just erroring in my opinion (in general, will work for your particular use case here but this code is fragile).
Was very hard to read some of those nodes, and you even cut one handler in half to help things there. For big graphs that you can’t screenshot entirely at full zoom, maybe stick it on https://blueprintue.com/ and link it in the post.
Good luck, let us know how it goes.
Hi!
Thank you for your response, before seeing this we did decide to redo the whole door blueprint, got rid of any cast to’s and started using interfaces. Also like you said we have moved the line trace into the character bp. So thank you for your input!
The problem we had being new was that we followed youtube tutorials that taught us this way, now realizing that they do the tutorials like that just for the speed of the tutorial and not the scalability of a game. Going forward I’ll be more conscious of following youtube tutorials ha.
All issues now sorted.
Thank you for the reply!
Awesome, glad you got things working better
Youtube can be a good resource, but there is unfortunately plenty of bad info there too. Recommend the ‘Don’t recommend this channel’ feature if you’re not aware of it already 
