Freeze-Tag uses the same UpdateType flags for some of its TagPackets as H&S and Sardines do.
But Freeze-Tag has another packet data structure that isn't matching IsIt, Seconds and Minutes.
Therefore the server wrongly interprets Freeze-Tag packets and updates its "seeking" and "time" metadata wrongly.
(These metadata fields are used to resend the TagPacket to later joining clients.)
This PR does the following changes:
479e37a7f4ecc22ec23b10f920c87d5d52386254
update: external actions in .github/workflows/ to the newest versions
189ac2dcd65ac1001d85b4b27e9fb31061937f6b
fix: Dockerfile to avoid 3 warning messages
765af57eb4afa342e97c907462be4c8237bad9a1
add: game mode detection in the first 4 bit of the TagPacket.UpdateType
change: parse the TagPacket for the metadata iff it is clearly for H&S or Sardines
change: only resend TagPacket to new clients for H&S or Sardines
Freeze-Tag uses the same
UpdateTypeflags for some of itsTagPackets as H&S and Sardines do. But Freeze-Tag has another packet data structure that isn't matchingIsIt,SecondsandMinutes. Therefore the server wrongly interprets Freeze-Tag packets and updates its"seeking"and"time"metadata wrongly. (These metadata fields are used to resend theTagPacketto later joining clients.)This PR does the following changes:
.github/workflows/to the newest versionsDockerfileto avoid 3 warning messagesTagPacket.UpdateTypeTagPacketfor the metadata iff it is clearly for H&S or SardinesTagPacketto new clients for H&S or Sardines