lsalzman
commented
2 years ago Reliable packets can trigger inclusion of the 16 bit sentTime field in the packet, but that's about it.
On Thu, Oct 28, 2021 at 12:58 PM playingoDEERUX @.***> wrote:
Hello,
I wanted to ask whether an ENetCommand or an ENetPacket comes with internal (32-bit) client time, because even though this may be modified, I wanted to use this for a few things. Or does it have to be included in my own protocol on top of ENet to communicate, I am looking if I am able to save some bandwidth/data here if ENet already includes this.
Thanks!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lsalzman/enet/issues/179, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALDVUNHR46AYJ5OPCJS6PTUJGFNLANCNFSM5G5LYNBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Hello,
I wanted to ask whether an ENetCommand or an ENetPacket comes with internal (32-bit) client time, because even though this may be modified, I wanted to use this for a few things. Or does it have to be included in my own protocol on top of ENet to communicate, I am looking if I am able to save some bandwidth/data here if ENet already includes this.
Thanks!