Difference between revisions of "PlaceAtMe"

1 byte added ,  15:05, 19 July 2006
Changed wording so people wouldn't use SetDestroy thinking they had solved the issue
imported>Gamall
m (spelling)
imported>ShadowDancer
(Changed wording so people wouldn't use SetDestroy thinking they had solved the issue)
Line 17: Line 17:
It can't be used with leveled ''items'', though. Leveled items are not supposed to be placed into the world - you can use them exclusively inside containers. Trying to create an item from a leveled list this way will just cause the yellow exclamation mark (Marker_Error.NIF) to appear.
It can't be used with leveled ''items'', though. Leveled items are not supposed to be placed into the world - you can use them exclusively inside containers. Trying to create an item from a leveled list this way will just cause the yellow exclamation mark (Marker_Error.NIF) to appear.


==Warning : Disable is not Destroy !==
==Warning : Disable does not Remove !==


Note that is is really unclear at the moment whether or not disabled PlaceAtMe'd objects are ultimately cleaned out of the savegames. Tests seem to show they are not, which can be a serious problem with spells that create lots of activators, for instance, and then disable them.  
Note that it is really unclear at the moment whether or not disabled PlaceAtMe'd objects are ultimately cleaned out of the savegames. Tests seem to show they are not, which can be a serious problem with spells that create lots of activators, for instance, and then disable them.  


So it seems only advisable to recommend the use of [[MoveTo]] on persistant references, whenever possible, instead of the couple [[PlaceAtMe]] / [[Disable]].
So it seems only advisable to recommend the use of [[MoveTo]] on persistant references, whenever possible, instead of the couple [[PlaceAtMe]] / [[Disable]].
Anonymous user