Masters of the Art
https://forum.guildofwriters.org/
What exactly does that mean? Colliding with a blocker crashes the client?Don't bother with this... blockers are still crashing Uru... Will have to find why.
In my humble experience, colliding with a blocker usually crashes my nose.diafero wrote:What exactly does that mean? Colliding with a blocker crashes the client?
ROTFL !tachzusamm wrote:In my humble experience, colliding with a blocker usually crashes my nose.
OK, I'll give it a try.diafero wrote:The person most likely to answer your questions is, I think, D'Lanor.
No. Scene object attributes are not netforced by default. They are only netforced when you set a hard netforce flag.Sirius wrote: There are still things I would like to know:
- are ptSceneObject.runAttachedResponder(state) and ptSceneObject.fastForwardAttachedResponder(state) netforced ?
Code: Select all
ptSceneObject.netForce(1)Code: Select all
ptSceneObject.netForce(0)I never managed to check because the sitting avatar's fat butt is always in the way.Sirius wrote: - is the clickable for a SittingModifier disabled for everyone in an Age when someone uses it ?
I doubt a programmer would automatically disable something that is out of reach anyway.PlasmaTypes.py does not give us any clues about netforcing or netpropagating of exclude regions. However, in order to do their job properly I suspect that they need to be either netpropagated or netforced. I'm guessing netpropagation because netforcing seems a bit strong for this.Sirius wrote: - are exclude regions netforced when controlled by a Python file ?
Good news ! Do you know what was crashing it, or was it a random bug ?diafero wrote:I was just able to setup up the wall, enter the wall area, climb it up, collide with a blocker, and then reach the top, on the DI Shard. So it seems those issues are fixed by now
Ok, great - these are used to run layer anims of blockers, and are played by every client. That would be really bad if they were netforced.D'Lanor wrote:No. Scene object attributes are not netforced by default. They are only netforced when you set a hard netforce flag.Sirius wrote: There are still things I would like to know:
- are ptSceneObject.runAttachedResponder(state) and ptSceneObject.fastForwardAttachedResponder(state) netforced ?Once this flag is set anything you do with the object will be netforced until you unset that flag with:Code: Select all
ptSceneObject.netForce(1)Code: Select all
ptSceneObject.netForce(0)
Hehe. For some reason Cyan did for the panel chairs... they even added an SDL var to check it isn't currently usedD'Lanor wrote:I never managed to check because the sitting avatar's fat butt is always in the way.Sirius wrote: - is the clickable for a SittingModifier disabled for everyone in an Age when someone uses it ?
. Looks really useless.Yes, there is only one other python file using exclude regions without responders, and there is no avatar check for it. So I guess the default value is not netpropagated. That's better, because on link-in a player automatically "clears" the region for the tubes.D'Lanor wrote:PlasmaTypes.py does not give us any clues about netforcing or netpropagating of exclude regions. However, in order to do their job properly I suspect that they need to be either netpropagated or netforced. I'm guessing netpropagation because netforcing seems a bit strong for this.Sirius wrote: - are exclude regions netforced when controlled by a Python file ?
It wasn't crashing, the server just kicked the client because it sent an unknown message (plClimbingMsg).Sirius wrote:Good news ! Do you know what was crashing it, or was it a random bug ?diafero wrote:I was just able to setup up the wall, enter the wall area, climb it up, collide with a blocker, and then reach the top, on the DI Shard. So it seems those issues are fixed by now
Actually that only happens when the player is alone. Note the return under "if len(PtGetPlayerList()):". Weird enough this also skips the ageSDL initialization in multiplayer mode. That does not seem right to me. I would move this section...Sirius wrote:Yes, there is only one other python file using exclude regions without responders, and there is no avatar check for it. So I guess the default value is not netpropagated. That's better, because on link-in a player automatically "clears" the region for the tubes.D'Lanor wrote:PlasmaTypes.py does not give us any clues about netforcing or netpropagating of exclude regions. However, in order to do their job properly I suspect that they need to be either netpropagated or netforced. I'm guessing netpropagation because netforcing seems a bit strong for this.Sirius wrote: - are exclude regions netforced when controlled by a Python file ?
Code: Select all
ageSDL = PtGetAgeSDL()
ageSDL.setFlags('nChairOccupant', 0, 1)
ageSDL.setFlags('sChairOccupant', 0, 1)
ageSDL.setNotify(self.key, 'nChairOccupant', 0.0)
ageSDL.setNotify(self.key, 'sChairOccupant', 0.0)
ageSDL.sendToClients('nChairOccupant')
ageSDL.sendToClients('sChairOccupant')