Trigger property signals may get lost?

Options
Thund
Thund ✭
in Photon Bolt
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

  • DirtyHippy
    DirtyHippy ✭✭
    Options
    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.
  • Thund
    Thund ✭
    Options
    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.

Cookies,
anyone?

We use cookies and related technologies to enhance your experience, show you personalised content and analyze performance and traffic on our website. By clicking on the „Accept All“ button you consent to the use of non-functional cookies and the subsequent processing of personal data to optimize our website and services as described in more detail in our Privacy and Cookie Policy.

By clicking on the „Customize or Deny all“ button you can decide otherwise. Clicking on the „Customize“ button will take you to a page where you can configure the usage of non-functional cookies (and related technologies) or deny all of them. You can access these settings at any time and also subsequently deselect cookies at any time in the footer area of our website.

ACCEPT ALL

Cookie Overview

We use the following categories of cookies and related technologies to enhance your experience, show you personalized content, and analyze performance and traffic on our website. We respect your right to privacy and accordingly you can chose to not allow some types of cookies (and related technologies). Click on the different category sliders and change our default settings to manage your cookie settings.

For more information on the specific cookies/related technologies we use and on how we use these, please see section 15 E. of our Privacy and Cookie Policy.

ABSOLUTELY NECESSARY

Authentication cookies we use are required to run our services … Cookies are required: Link

FUNCTIONAL AND MARKETING COOKIES

These cookies collect anonymous data and allow us to optimize our website and user experience. These cookies are listed here:

ANALYTICS

Help us to understand how visitors interact with our services, enables us to analyze and improve our services (also through third party analytics).