Phil's Relto Problems

[D'Lanor]

That way you could test "Are SDL variables for this age working?"

The window shutters are working fine and they show up correctly at re-linking. So at least when modified in-game the SDL variables work.

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?

[rarified]

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?

[Mac_Fife]

Still no sign of Phil's vest, but at 15:18 Ki time the Ferry tunnel and Takotah alley Bahro stones were both showing in the public city. So at least I'm now conviced that the Ferry Tunnel one does appear in the public instance!

[rarified]

... but at 15:18 Ki time the Ferry tunnel and Takotah alley Bahro stones were both showing in the public city. So at least I'm now conviced that the Ferry Tunnel one does appear in the public instance!

Ok, so I'll close any bugs related to that. The *Chance variables are now set at 33%.

[D'Lanor]

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?

But what happens with the global SDL value once it has been fetched by the client? Is it stored in the age vault or in the age SDL state?

[a'moaca']

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...

[oldmanjob]

I have not been able to get to Phil's Relto, with any of my avies either through the linking stone book or going the long way around through teledahn. When I get out of the game I get the message that it is a SDL Disk Problem.

[ametist]

Same experience here, this is the logfile :

[Gwyn2]

Hi everyone! I'm not sure where to post this, but the only problem so far is crashing to desktop while trying to link
into Phil's Relto. It just happened & last night (before scheduled maintenance) it happened twice.

Gwyn2
Gwyn H

[rarified]

Thanks... I'll look at it when I get home in a couple of hours.

_R