Difference between revisions of "Talk:PlaceAtMe"
m
added a header to separate the two distinct discussions about placeatme
imported>Gamall (As expected, deleteFullActorCopy does not work.) |
imported>Gamall m (added a header to separate the two distinct discussions about placeatme) |
||
| Line 20: | Line 20: | ||
--[[User:Tegid|Tegid]] 09:14, 20 April 2006 (EDT): It turns out the answer to my questions are no, you don't need a persistent reference, and yes, one object can create another of the same type. | --[[User:Tegid|Tegid]] 09:14, 20 April 2006 (EDT): It turns out the answer to my questions are no, you don't need a persistent reference, and yes, one object can create another of the same type. | ||
==PlaceAtMe and Disable== | |||
-- I noticed something bad about the couple PlaceAtMe / Disable, often used in mods for spell effects. Once the references are placed, there is no way to get rid of them. Although disabled, they are saved with your saved games. In MW there was a way around this, but the command disappeared with TESIV. All I can say is that, unless there ''is'' a way around this, modders should strive to avoid use of PlaceAtMe at all cost, and use MoveTo instead on a finite number of references. [[User:Gamall|Gamall]] 12:23, 18 July 2006 (EDT) | -- I noticed something bad about the couple PlaceAtMe / Disable, often used in mods for spell effects. Once the references are placed, there is no way to get rid of them. Although disabled, they are saved with your saved games. In MW there was a way around this, but the command disappeared with TESIV. All I can say is that, unless there ''is'' a way around this, modders should strive to avoid use of PlaceAtMe at all cost, and use MoveTo instead on a finite number of references. [[User:Gamall|Gamall]] 12:23, 18 July 2006 (EDT) | ||
| Line 76: | Line 78: | ||
:::I've tested this myself, and Gamall is right - objects created using placeAtMe are not cleaned out of the savegame, whether disabled or not. It doesn't seem to matter how long you wait, or how much traveling you do. For the record, '''deleteFullActorCopy''' has no effect on normal objects. I'm not sure why anyone would expect it to. [[User:Scruggs|Scruggs]] 18:44, 18 July 2006 (EDT) | :::I've tested this myself, and Gamall is right - objects created using placeAtMe are not cleaned out of the savegame, whether disabled or not. It doesn't seem to matter how long you wait, or how much traveling you do. For the record, '''deleteFullActorCopy''' has no effect on normal objects. I'm not sure why anyone would expect it to. [[User:Scruggs|Scruggs]] 18:44, 18 July 2006 (EDT) | ||
::::I've tested deleteFullActorCopy nevertheless. As expected, it does not seem to have any significant effect. So I'm afraid we'll have to stick with MoveTo...[[User:Gamall|Gamall]] 19:24, 18 July 2006 (EDT) | ::::I've tested deleteFullActorCopy nevertheless. As expected, it does not seem to have any significant effect. So I'm afraid we'll have to stick with MoveTo...[[User:Gamall|Gamall]] 19:24, 18 July 2006 (EDT) | ||
---- | |||