![]()
|
|
The easiest and most straightforward fix for this is to have the retro script attach the workshop object to the non-persistent container via a script call to SetLinkedRef() [I sure wish we had this in Skyrim]. The reason for this is that you cannot directly edit the workshop object's list of linked refs itself because of an engine bug.
So when the update fires off its retro script, this container will be properly linked, and as a result, also be flagged persistent because the container is now associated with a script property.
So when the update fires off its retro script, this container will be properly linked, and as a result, also be flagged persistent because the container is now associated with a script property.
After having checked other settlements, the only container any of them have that should be 2-way linked with the Workbench is the primary box. No settlement also has the secondary box connected in this manner. So I do not think that hooking the farm box up for Tenpines Bluff is going to behave any differently that any other settlement where the farm box isn't hooked up this way.
Now, there ARE some settlements where the primary box isn't 2-way linked and I believe that to be a bug but that should be filed in a separate ticket.
Now, there ARE some settlements where the primary box isn't 2-way linked and I believe that to be a bug but that should be filed in a separate ticket.
Showing Comments 1 - 2 of 2