Hi,

I have a question. I read through:
http://www.creationkit.com/OnUpdate_-_Form#Notes
http://www.gamesas.com/topic/1349327-scripting-savegame-bloating/
http://www.gamesas.com/topic/1358788-script-causes-savegame-bloat/page__p__20495082__hl__savegame%20bloat__fromsearch__1#entry20495082

I use onupdate heavily and the shortest is 1 sec. Why is it that my mod causes bloat when I remove it from the load order and load a savegame with the mod active? Will using state or registerforsingleupdate at the end of onupdate be enough to help here?
I haven't done http://www.creationkit.com/DumpPapyrusStacks as I just recently read it from one of the above links.

I guess DPS is the only point to find out what is causing the bloat? Are scripts endlessly running even though the mod is no longer loaded?

If you use RegisterForUpdate(), yes, the scripts will continue to attempt to execute even after the mod is uninstalled. That is why you should never, ever, ever use it. Use RegisterForSingleUpdate() instead.

So basically, because of registerforupdate my scripts are registered, are in the queue but can't be executed because the mod is not loaded and thus, increase the save size astronomically?
I changed now to singleupdate but I must start a new game to have the change take effect, right?
Are there other known causes for bloat? Of course, we all know the placeatme thing.

I don't. Tell me about the PlaceAtMe thing.

PlaceAtMe is better now than it was in Oblivion.

So it will remove objects now?
So it seems that only really registerforupdate may cause bloat.

PlaceAtMe does not auto remove/delete anything as that would be a terrible idea as some things you do not want auto deleted.

There are now functions that will delete objects that were dynamically created unlike Oblivion that did not have this feature.

Delete and DeleteWhenAble should be used in conjunction with PlaceAtMe.

Ah, okay, that makes me feel better. I'm always careful to cleanup my mess, particularly when I'm using hundreds of FXEmptyActivators in a script to guide movement... if just using PlaceAtMe caused bloat, I'd be so screwed

ObjectReference PlaceObjectHere = RefToPlaceTheObjectAt.Placeatme(Object) will link the Object to a reference, casting this reference as perm to a quest prop lets you safely delete the ref again like this

QuestScript property ScriptQuest Auto

Script has the property tRef as ObjectReference

so

Event OnSomething()
QuestScript.tRef = PlaceObjectHere
;do something with the ref now
endevent

Event NextEvent()
;we are done delete the object again
QuestScript.tRef.Disable()
QuestScript.tRef.Delete()
endevent

this should prevent bloating with placeatme, for the OnUpdate it would be best to use OnSingleUpdate or just set up conditions that contain UnregisterForUpdate, like:

Event OnUpdate()
if Condition == 0
UnregisterForUpdate()
else
;do some stuff
endif
Endevent

when you disable the mod the condition will be always 0 so your script should in theory unregister itself upon disabling of the mod, as the alias is stored inside the savegame.