Draft
Conversation
Contributor
|
net has downsides to umsg, e.g. it can trigger on the client before an entity it's networking is actually networked. umsg should be preferred for applications where data sent is small. |
Contributor
Author
|
Does it make a difference? Entities outside of PVS will be invalid regardless of the networking method used |
Contributor
|
I might be misremembering, but I think umsg is safer from errors or messages that can't complete due to invalid entity. Starfall uses a queue of its own to retain net messages until entity is valid, but I probably could've just used umsg the whole time instead. |
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
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.
Converts all umsg to net to modernize the code and make networking a little cheaper (not tested yet)