Serious bug: Local variable persistance lost in localvault

[Ronan]

This is something I didn't know of until we did the horses in NWN1. I just tested it in NWN2 and confirmed: local variables on items are erased when a PC is saved to a local vault. For this reason, we won't be able to count on data stored on items, at least not from a blueprint itself, due to DMs bringing them in-game via a local DM vault avatar. When I can update with the DM client I'll test if the DM avatars store variables, but I doubt they will.

Whether or not we'll be able to count on PCs never being imported locally - I really don't know. I suspect that depends a lot on our vault setup, and backups.

So we either need,
a) A vault setup reliable enough to ensure local backups never need to be used.
or,
b) To store item (and PC) data on a global database.

[Ronan]

Bool feels confident the new vault will have a good enough backup system that local vault replacements will be unnecissary. This only leaves DM client worry, which I will test when I get the client.