Python confusion

[boblishman]

did you make your new animated object an ACTOR .... if you assign an IPO animation to an object that is not an ACTOR ... thats a guaranteed crash to desktop

[Justintime9]

That did it (can't believe I didn't notice it wasn't an actor ) It's clickable, but doesn't do anything (I probably just have to move the Avatar Empty or something)

[diafero]

As the comment in SDL files created by PlasmaShop, and in all Cyan files, states, you must NEVER change an existing version of an SDL STATEDESC block, Offline, this will result in new variables simply being ignored. Online, it can cause a crash of the game server and all clients linking there.
Instead, you ALWAYS have to copy the last version of your SDL (the last block), increase the version number and then do your change. That is necessary for every kind of change (except for comments, of course): No matter whether your add, remove, rename a variable, change it's type or whatever, you have to copy your last block and only edit the new one, having an increased version number. You can do multiple changes in one go though, like adding 5 new variables and changing some others with one version change.

I assume your SDL file looked like this so far:

Code: Select all

STATEDESC Zefora
{
    VERSION 1

    VAR BOOL    WindowOpen[1]    DEFAULT=0 DEFAULTOPTION=VAULT
}

In that case, it should now be:

Code: Select all

STATEDESC Zefora
{
    VERSION 1

    VAR BOOL    WindowOpen[1]    DEFAULT=0 DEFAULTOPTION=VAULT
}

STATEDESC Zefora
{
    VERSION 2

    VAR BOOL    WindowOpen[1]    DEFAULT=0 DEFAULTOPTION=VAULT
    VAR BOOL    LidOpen[1]    DEFAULT=0 DEFAULTOPTION=VAULT
}

[D'Lanor]

Hmm, I never had problems offline keeping the same version number as long as I make sure to delete the sav file (which you should always do when testing new versions).

And yes, online it will result in SDL Hell. In fact the age and sdl files are the only files which have to be installed on the shard itself (the game server), but one must make absolutely sure that server and clients are updated at the same time. I believe UU was somewhat more tolerant about it than alcugs. It would only crash the clients.

[diafero]

I believe UU was somewhat more tolerant about it than alcugs. It would only crash the clients.

Well, it could be that the server refuses to load ("crashes" in terms of exits, but in a controlled way) if it finds an invalid (due to not being able to read since the SDL changed) saved age state. But in the end it does not matter who crashes, it makes it impossible to visit the age

SDL Hell.

Almost as bad as DLL Hell, isn't it?

Hmm, I never had problems offline keeping the same version number as long as I make sure to delete the sav file (which you should always do when testing new versions).

Right, but I thought it'd be better to already tell people what needs to be done in case we can play these ages online