Trigger property signals may get lost?

Since we are using UDP, I guess that if I use a property of type Trigger, there are great possibilities that such signal will get lost and clients would never receive it, am I right? Is it better to use Bool properties instead to check for their value and act in case it is different?

Comments

  • It seems you fundamentally misunderstand how Bolt handles packets. Please read this:

    https://doc.photonengine.com/en-us/bolt/current/community-wiki/extra-bits/packets

    Bolt sends one packet per send tick that is an aggregation of everything that it can fit.

    Triggers are special cases and are unreliable (but rarely) - unlike the rest of state which is reliable. Triggers also have extra logic in them to ensure they try to fire on the correct server frame on the client.
  • DirtyHippy wrote: »
    It seems you fundamentally misunderstand how Bolt handles packets. Please read this:

    https://doc.photonengine.com/en-us/bolt/current/community-wiki/extra-bits/packets

    Bolt sends one packet per send tick that is an aggregation of everything that it can fit.

    Triggers are special cases and are unreliable (but rarely) - unlike the rest of state which is reliable. Triggers also have extra logic in them to ensure they try to fire on the correct server frame on the client.

    Hi DirtyHippy,

    Thank you very much for your answer. I already knew about how Bolt manages the packages, but I did not find information (my fault, probably) about how Triggers fit into that process. If you say they are unreliable that's new to me and was the answer I was looking for, thanks again.
Sign In or Register to comment.