Fix YojimboClient state update logic #191
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.
When running some tests I noticed that the
YojimboClient
would sometimes sets its state toCLIENT_STATE_CONNECTED
before the server would execute theOnServerClientConnected
callback. Looking at the current logic theYojimboClient
sets the state toCLIENT_STATE_CONNECTED
when the netcode state isNETCODE_CLIENT_STATE_SENDING_CONNECTION_RESPONSE
rather than when it isNETCODE_CLIENT_STATE_CONNECTED
.This PR fixes that.