Difference between revisions of "SetPosition - ObjectReference"

→‎Notes: setmotiontype problem
imported>Catwheezle
(→‎Notes: added forcegreet.)
imported>DavidJCobb
(→‎Notes: setmotiontype problem)
 
(4 intermediate revisions by 3 users not shown)
Line 27: Line 27:
== Notes==
== Notes==
* SetPosition() should be avoided for placing other actors in sight of the player, as they will suddenly appear in an unrealistic way. Instead, consider placing them nearby but out of sight, and making them approach the player themselves, using [[PathToReference_-_Actor|PathToReference]] or [[ForceGreet (Procedure)|ForceGreet]].
* SetPosition() should be avoided for placing other actors in sight of the player, as they will suddenly appear in an unrealistic way. Instead, consider placing them nearby but out of sight, and making them approach the player themselves, using [[PathToReference_-_Actor|PathToReference]] or [[ForceGreet (Procedure)|ForceGreet]].
* All movement functions can cause [[SetMotionType - ObjectReference#Bugs|major issues]] when used on a reference that has had a [[SetMotionType - ObjectReference|motion type override]] applied.


== See Also ==
== See Also ==
*[[ObjectReference Script]]
*[[GetPositionX - ObjectReference]]
*[[GetPositionX - ObjectReference]]
*[[GetPositionY - ObjectReference]]
*[[GetPositionY - ObjectReference]]
*[[GetPositionZ - ObjectReference]]
*[[GetPositionZ - ObjectReference]]
*[[PlaceAtMe - ObjectReference]]
*[[MoveTo - ObjectReference]]
*[[MoveToInteractionLocation - ObjectReference]]
*[[MoveToMyEditorLocation - ObjectReference]]
*[[MoveToMyEditorLocation - ObjectReference]]
*[[MoveToInteractionLocation - ObjectReference]]
*[[ObjectReference Script]]
*[[PathToReference - Actor]]
*[[PathToReference - Actor]]
*[[MoveTo - ObjectReference]]
*[[Spatial functions and snippets]]
*[[Unit]]
Anonymous user