Conversation
also don't know if having a separate NetworkController is actually needed at all
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This branch adds a Host and Client scene and a foundation for a
NetworkController, which will allow for networked play. The purpose is to allow us to test networked games with more than one player and we can begin writing events for it to really work. Right now, if a person joins as a host, they will be the bunny, and everyone else will be a carrot.This was taken from the networked physics lab, and everything is currently quite primitive as
NetworkControlleris not complete, this might not follow the arch spec, and the Scenes hold the networking logic. So this will be a future TODO item.