Server: Delta snapshot developer print fix #317
Merged
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.
Since 3f92ee4 client->deltaMessage is set to
client->netchan.outgoingSequence - (PACKET_BACKUP + 1)
as a way to disable delta snapshots. Developer warnings like "Delta request from out of date packet" are not printed when client->deltaMessage matches this exact expression, but asclient->netchan.outgoingSequence
is incremented, warning messages may be printed when they shouldn't be.This fix restores the behavior that client->deltaMessage is set to -1 to disable delta snapshots, allowing developer prints to correctly distinguish between delta being disabled intentionally versus by PACKET_BACKUP limit.