DebugMessage #4
Open
DebugMessage #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tries to parse the stream with increaseing sizes of unknown messages; not really tested just used it for the unknown NetMessageType 34;
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When in DEBUG this message is used when a unknown NetMessageType is encountered. The DebugMessage first assumes it has a length of 1 and tries to parse the rest of the stream. Increasing the size and restarting the parse whenever it encouters an error. If the remaining stream can be parsed successfully we Debug.Write that size for further investigation.
not really tested just used it for the unknown NetMessageType 34 (/pull/3)
could maybe figure out the length of multiple unkown messages but i have it set up so it restarts when it finds the second unknown message (to try an other size). Also never tested this!