|
|
Post by Sniffles on Jul 31, 2015 7:08:17 GMT
I don't think that mod could suppose any problem corruption wise. My guess is the containers are either activators attached to a script activating player character with the real container, thus allowing it to be done from different places, or, instead of scripts, ash like activators could have used, for a more direct approach. It will increase CPU/GPU strain when loadding those cells, as it add items there, but from a save size point of view, the only effect I can foresee is less items stored in obscure locations you then forget about, thus few bytes less in the save size. Of course, the author could have done something really clumsy at some point, but that can be applied to any mod. I can't see any problem attached to the described features, size or corruption wise. So let me make a dumb guess. This container is a list attached to the PC instead of a location? |
|
|
|
Post by amgepo on Jul 31, 2015 15:17:52 GMT
Well, I don't know the method the mod author used, since I did not examined the mod, but the usual way to do these things launching a script when the player activate the local container, that makes the player activate the shared container. You activate one, then your character activate the real one, regardless from where did you do that. The other method, more obscure, but the one I would have use, is using an ashlike activator (when someone is reduced to ashes, it's body remain hidden and the ash pile append to it when you activate it, if you assing an ash object to a live character, you will open the dialogue instead). You can assign various ash like activators using the local container for that, that will append to the shared container, without even using a script.
|
|
