Make solo trigger activations use non-reliable packets #48
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
|
BTW All solo triggers are reset 0.0s no matter what number is put in there. That property is just ignored with solos. Same with the amount of times a trigger can reset. It's always infinite with solos. 😛 |
Commit 7459553 added a |
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.
Normal trigger activations are non-reliable. Reliable causes extreme network load and eventually DCs in MP servers with high server FPS and player standing in solo trigger with reset of 0.0s.
Not sure why this originally used reliable. My understanding (unconfirmed) is that PF did not do this. This change will need to be thoroughly tested before potential merge.