Skip to content

cannon destinations actually working, but very fast ones cause other problems #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cacology wants to merge 1 commit into
base: main
Choose a base branch
from
Open

cannon destinations actually working, but very fast ones cause other problems #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/routes/core/reference/destinations/+page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,11 +82,11 @@ If finer permissions is enabled: `multiverse.teleport.self.pl.<playername>`

## Cannon Destinations

:::caution[unfinished]
Cannon destinations are not implemented in MV5 yet
:::
The thing you have to remember with Cannon Destinations is that **you will never see a cannon**. This basically creates an exact destination with a velocity. The reason it's a different dest type entirely is due to the fact that we have provided a convince method: `cannon-X` where X is a velocity.

Too high speeds for cannon destinations can fail. The `moved-wrongly-threshold` and `moved-too-quickly-multiplier` in `spigot.yml` can be increased--`.inf` sets them to infinity, effectively disabling them--but even with these high thresholds very high speeds can trigger other failures.


### Examples

`/mvtp cannon-2`
Expand Down