Difference between revisions of "Talk:CreateFullActorCopy"

Talk:CreateFullActorCopy (edit)

793 bytes added , 02:08, 7 November 2009

Anonymous user

@@ Line 178: / Line 178: @@
 :I'm not certain that Create/DeleteFullActorCopy have ever been thoroughly tested. That said, assuming they work correctly, yes, that should be fine. AddItem does not create a reference and therefore does not add bloat. And RemoveAllItems is a common way of getting rid of bloat (as documented by QQuix)
 :[[User:DragoonWraith|<span style="font-family: Oblivion, Daedric Runes; size=2;">D</span>ragoon <span style="font-family: Oblivion, Daedric Runes; size=2;">W</span>raith]] [[User_talk:DragoonWraith|<span style="font-family: Oblivion, Daedric Runes; size=2;">TALK</span>]] 13:48, 27 April 2009 (EDT)
+::A better option might be to simply use placeatme with a leveled list that contains the skeleton that has static equipment, instead of creating a copy. Although this may seem like a worse idea given the bad reputation placeatme has, calling removeme on placeatme'd actors, and not giving them any scripted items seems to alleviate all unusual bloat. Using a leveled list to create the skeleton, instead of the actual reference is just there for extra protection to ensure that the skeleton will be cleared upon next cell reset and to keep the skeleton from having any persistence. Createfullactorcopy is designed mostly for use with NPCs or instances where the type and appearance of the actor to be copied cannot be known beforehand.--[[User:Vagrant0|Vagrant0]] 02:08, 7 November 2009 (EST)