Branan wrote:diafero wrote:So if a DEFAULTOPTION=Vault variable is changed in the vault, there is no way to override it locally in an age, even by changing it *after* the global change?
I'm not sure. I've never tried to change a DEFAULTOPTION=Vault variable on the gameserver, just in the age instance vault.
I should mention, I got my info on this from Hoikas, who's done quite a bit more work trying to figure out how SDL blobs get merged than I do. It's possible DEFAULTOPTION=Vault only applies if the gameserver value is at the default value, and if it's not the normal "whichever is newer" rule applies. That would jive better with the actual text.
As far as I know, none of Cyan's code changes a DEFAULTOPTION=Vault variable on the gameserver, just in the local and global vault blobs. I'd say anything we don't see used from Cyan is considered "undefined behavior"