fix: only parse time & seeking from TagPackets for Hide&Seek or Sardines #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Freeze-Tag uses the same
UpdateType
flags for some of itsTagPacket
s as H&S and Sardines do.But Freeze-Tag has another packet data structure that isn't matching
IsIt
,Seconds
andMinutes
.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:
.github/workflows/
to the newest versionsDockerfile
to avoid 3 warning messagesTagPacket.UpdateType
TagPacket
for the metadata iff it is clearly for H&S or SardinesTagPacket
to new clients for H&S or Sardines