Fix packet details of ENetConnection EventType EVENT_RECEIVE documentation
#80182
Conversation
This file contains 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
akien-mga
changed the title
akien-mga
changed the title
|
Thanks! And congrats for your first merged Godot contribution 🎉 |
akien-mga
changed the title
EventType EVENT_RECEIVE documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…ntation
The documentation for
ENetConnection#serviceexplains correctly that packets are queued in the associatedENetPacketPeer, however the documentation forEventType<enum ENetConnection_EventType>#EVENT_RECEIVEincorrectly states that the received packet is placed in the array returned fromENetConnection#service. This PR updates the documentation forEVENT_RECEIVEto correctly state that the packet is queued in the associated peer.