cannon destinations actually working, but very fast ones cause other problems#29
Open
cacology wants to merge 1 commit intoMultiverse:mainfrom
Open
cannon destinations actually working, but very fast ones cause other problems#29cacology wants to merge 1 commit intoMultiverse:mainfrom
cacology wants to merge 1 commit intoMultiverse:mainfrom
Conversation
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
1 participant
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 combines two issues:
Multiverse/Multiverse-Core#3425
and
Multiverse/Multiverse-Core#3426
Cannon destinations do work, so the documentation shouldn't have a warning. However, very fast speeds fail. If someone has a better technical understanding of why very fast speeds don't work, it would be nice to add it.
Respectfully submitted,