J'Kla wrote:I hacked a copy into word just so I could make some sort of a list and even reducing to a small font it ran to 47 pages.
Like I said, you only need to consider the latest version of any particular entry (Version 43 in this case), so you can cut that down a lot.
J'Kla wrote:I can't find a reference to globalsdl in the Plasma Console pdf but it won't do me any harm to experiment.
What PDF is this?
J'Kla wrote:I was just wondering is there a way to set these dirtsand console boolean values from that Plasma Console in game?
Yes, you can set it per-Age with the Age.SetSDL* commands (though I've never quite understood when they work or won't -- I use the Plasma Python Console instead). Remember to use the in-game help (?) or the exported documentation for more information.
J'Kla wrote:I presume there is some way to make and implement a script to set a batch of these variables to particular state.
Not that I'm aware of. It's easier to just set the defaults the way you want in the SDL files before initializing your vault (or doing a vault wipe and rebuilding once you have it the way you want).
J'Kla wrote:If I edit the SDL to set up particular state and then make sure both my local and dirtsand SDL have the same data would that change my dirtsand to have a particular state for my edition?
Yes, but with some caveats. First rule is to make sure that both copies are identical. Client and Server need the same SDL files. Second rule is that if you make any changes, you need to do them in a new version of the SDL entry. These are both details that have been widely known for Age authors since 2004, so I'm sure you're aware of those. However, generally speaking, editing the values in the SDL files won't automatically update values in an Age that already exists in the database. The SDL files provided by the moul-scripts repository are largely as provided by Cyan, with the ridiculously-long history of MOULa's edits. You can pare them down to a single version on each (the latest) for your fresh server and have a lot less to deal with. This is essentially what we did with
Gehn's SDL files. As you can see, our
city.sdl only has two versions in it (
the second was added to adjust the bahro stone values), which is a lot more manageable. You only have to be internally-consistent with your own server, after all.