rarified wrote:D'Lanor wrote:However, when you configure the AllAgeGlobalSDL...etc. on the server you are modifying the age vault instead of the age SDL state, isn't it? In an ideal world these should synch automatically, but could it be that the difference in names is throwing off the MOSS synching routine?
That would impact state changes from within the game, but here we're setting the global SDL which should be fetched by all clients, right?
D'Lanor's closer -- the global SDL is merged in automatically by the server (and not ever looked at by clients). The thought that a case mismatch was causing this process to miss the global change was exactly the final point of my previous wrong theory. There may still be something going wrong with it somewhere, and it seems likely since this age with the mismatched names is affected while others are not apparently affected.
One minor point, and this is getting farther away from the shard discussion itself, there are actually three pieces of state, the age state D'Lanor referred to as working, the "age vault" D'Lanor referred to, AND the global state. MOSS merges them all. I received a note last night that an error was happening loading the "age vault" state due to the case mismatch, but as that particular state should never be changed away from default in this particular age I doubt that's the bug. Not sure yet, though; I'm quite open to possibility at this stage...