Blue print set actor location / relative

There seems to be no difference whether I use set actor location or set actor relative location, they both do the same thing resulting in a few headaches for positioning my character.

Ah, you are right there… okay. I was looking at it from a different perspective of relative to current position in the world, not based on its root… if that makes any sense. Thanks

Well there is diffrence, as api reference suggest relative location sets relative location of root component regardless if its movable or not

Where set actor location tries to move root component but if something blocks location or rootcomponent is not movable it will fail and return false

Look on source code snippits