Actor : SetActorLocation <---- Why isn't it SetActorWorldLocation?
Component : SetWorldLocation
Actor : SetActorLocalLocation <---- Why doesn't it exist?
Component : SetLocalLocation <---- Why doesn't it exist?
Actor : SetActorRelativeLocation
Component : SetRelativeLocation
Actor : AddActorWorldOffset
Component : AddWorldOffset
Actor : AddActorLocalOffset
Component : AddLocalOffset
Actor : AddActorRelativeLocation <---- Why doesn't it exist?
Component : AddRelativeLocation
--> Do Location and Offset have the same meaning?
--> Do Local and Relative have the same meaning?Presumably because it’s always the world location, I guess they thought it would be redundant to have “World” in the name when there’s no “Relative” version (what would it be relative to? There’s no parent actor)
Not sure, guess they thought Offset better described it.
Because there’s nothing to be relative to.
Do Location and Offset have the same meaning?
Only in the context of Local Offset.
Do Local and Relative have the same meaning?
Not exactly. Local would be in the component’s space, relative would be relative to its parent. Though I can’t think off hand where that would actually be different.
But why does actor have SetActorRelativeLocation ? That is why the nomenclatures are confusing, overwhelming and burdens users to remember such anomalies.
No idea, you’d have to ask Epic.
SetActorRelativeLocation just calls the SetRelativeLocation on the root component and a relative location on the root component should logically be the same as the absolute as there’s nothing for the root component to be relative of.