I have a blueprint that says if player overlaps with a collision sphere, a component from that blueprint (An object and a collision cube inside it) has its location set and should be teleported elsewhere. But the object stays where it started and it doesn´t go to the location it should, even though the rest of the commands work properly.
Any ideas on whats the problem and how to fix it?
Hi!
One thing I’d check is the actor reference you’re using in your OnActorBeginOverlap event.
The event has two actor outputs:
Overlapped Actor: the actor whose overlap event is firing, usually the actor containing the trigger.
Other Actor: the actor entering the overlap, in your case presumably the player.
If you’re checking for the player or using the overlapping actor to drive your logic, make sure you’re using the correct reference. You can connect Other Actor
If you’ve already doing this, could you share the actual Blueprint logic that’s supposed to move the object, including the location setting nodes? The screenshot of the overlap logic helps, but seeing the full chain would let us diagnose the problem more precisely.
DorrealArt’s check on Other Actor is the right first step. If the overlap path is already correct and the rest of the chain still runs, the usual reason Set World / Set Relative Location “does nothing” is that the component is not free to move.
Check these in order:
Mobility – Select the mesh + collision cube you are teleporting. In Details → Transform, Mobility must be Movable. If it is Static (or the parent actor is Static), the set-location call is ignored at runtime even though the Blueprint compiles and the rest of the graph fires.
Relative vs world – If that component is still attached to the actor root (default), Set World Location moves it in world space for one frame, then the attachment can snap it back relative to the root on the next tick. Prefer either:
Set Relative Location with an offset written in the parent’s local space, orSet Actor Location if both the mesh and the cube should stay together.Physics – If Simulate Physics is on for the mesh or the cube, Set … Location fights the physics body. Either turn Simulate Physics off for the teleport, or use Set World Location on the primitive with Teleport / SetAllPhysicsPosition / disable simulation for a frame.
What you are actually moving – Make sure the target pin is the component you think it is (the child mesh/cube), not a different instance. Print Get World Location before and after the set on that same component reference; if the printed value never changes, the pin is wrong or Mobility/physics is blocking it.
Collision cube inside a mesh component – Nested components inherit the parent’s transform. Moving only the outer mesh and expecting the cube (if it is a separate component) to follow only works if the cube is a child of that mesh. If both are siblings under the root, move both, or parent the cube under the mesh.
Quick test: temporarily call Set Actor Location on self to a known spot in the same event. If the actor jumps but the child still does not, it is almost certainly Mobility, attachment, or physics on that child.