Actually if you are taking actions via Subscribe SitEventType.Start and Subscribe SitEventType.End, if the agent occupying the sit decided to logoff or leave your experiece, the subscription for END will never be triggered. So, in very usual scenarios like : Nobody can use this object if the sit are occupied, this sit will be occupied 'til a new instance of the experience decides to start. It's really bad.
#SitEventType.End should fire when an agent leave the experiece or logout.
exotic snow
ebon badger
You could listen also for agent exit event to correct for that. Technically the avatar did not perform an unsit action, it did a logout/leave, this might be relevant when an unsit event triggers something that assumes the avatar is still around
exotic snow
I believe that the purpose of the unsit event is to notify that the av is no longer occupying the seat. So, technically you are right...But it's rubbish since the purpose is as I said: to notify a status change on the sit. I can use this suggested workaround, but it's a dirty workaround.
ebon badger
Alot of things should be improved in the scripting api, because of said spaghetti code, the way the api is written forces you to write such code. There are better ways to write single threaded async code which I want to fix, I just worry it is not a well known style of coding in c# and people might not like it, even if it's superior
exotic snow
Well..I am a C# coder, Azure Native Software Engineer and I will love it. So, plz implement it.
spice harness
Hi @exotic snow , I'm trying to discover things now...
I know the SitEventType has relationship e.g. an occupied vehicle, or never resetted position for grabbed dynamic objects.
Can you give me an example where the behaviour you said happens?
e.g. if I seat in a chair, could be an example? if I seat on a chair and there is a and the agent occupying the sit decided to logoff, will this block the chair?
exotic snow
Hey @spice harness (Fala Português ? I hope so !) ...yeah...it's easy to reproduce...
Just put any object with seat points and ofc, a sit subscription script to handle Start and End....Then...Logoff or open codex and go to somewhere else.
Expected result: Subscription End triggered.
What happen: Nothing - It's like the agent is still occupying the seat.