Updated Destinations (markdown)

FernFerret 2011-09-23 06:49:02 -07:00
parent ad58c6e864
commit 1905f32e38
1 changed files with 8 additions and 7 deletions

@ -8,7 +8,7 @@
* [[Portal - Requires MV-Portals|Destinations#wiki-portal]]
* [[OpenWarp - Requires OpenWarp|Destinations#wiki-openwarp]]
## <a name="world"></a>World Destinations
## <a name="world" href="#wiki-world"></a>World Destinations
`/mvtp world`
`/mvtp world:n`
`/mvtp w:world`
@ -20,7 +20,7 @@
World destinations can be prefixed with a `w:` but it is not required. If no prefix is found for a destination, it is assumed to be a world. You can also add a direction to spawn a player in a world just like with portals.
## <a name="exact"></a>Exact Destinations
## <a name="exact" href="#wiki-exact"></a>Exact Destinations
`/mvtp e:world:0,0,0`
`/mvtp e:world:0,0,0:0:0`
@ -30,7 +30,7 @@ World destinations can be prefixed with a `w:` but it is not required. If no pre
Exact destinations are useful if you know exactly where someone should spawn, but they're difficult to set, as that's a lot to type! Luckily, an easy way of setting an exact destination is by using: `/mvpm dest here` this will set the destination to an exact dest of your current location, __including where you are looking__. This is great if you want people to spawn looking at your awesome creations!
## <a name="player"></a>Player Destinations
## <a name="player" href="#wiki-player"></a>Player Destinations
`/mvtp pl:fernferret`
**Permissions**
@ -39,7 +39,7 @@ Exact destinations are useful if you know exactly where someone should spawn, bu
Player destinations are exactly what they sound like, they will always teleport you to a _specific_ player! If that player is not online, you will not teleport, or if you're using a portal, it will act as if it's inactive. If a player tries to teleport to themselves, nothing will happen.
## <a name="cannon"></a>Cannon Destinations
## <a name="cannon" href="#wiki-cannon"></a>Cannon Destinations
`/mvtp cannon-2`
`/mvtp ca:world:x,y,z:pitch:yaw:speed`
@ -49,7 +49,8 @@ Player destinations are exactly what they sound like, they will always teleport
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.
## <a name="bed"></a>Bed Destinations
## <a name="bed"></a>
## <a name="world" href="#wiki-world"></a>Bed Destinations
`/mvtp b:mybed`
**Permissions**
@ -58,7 +59,7 @@ The thing you have to remember with Cannon Destinations is that __you will never
Takes a player to the bed they will spawn at if they die. This can only take players to their own beds at this time, not others' beds.
## <a name="portal"></a>Portal Destinations - _REQUIRES:_ [Multiverse-Portals](https://github.com/Herocraft/Multiverse-Portals/wiki/)
## <a name="portal" href="#wiki-portal"></a>Portal Destinations - _REQUIRES:_ [Multiverse-Portals](https://github.com/Herocraft/Multiverse-Portals/wiki/)
`/mvtp p:portal`
`/mvtp p:portal:n`
`/mvtp p:portal:sw`
@ -71,7 +72,7 @@ These are examples of the `PORTAL` destination type. Portal destination types ar
TODO: Document the `here` functionality when you're standing inside a portal.
## <a name="openwarp"></a>OpenWarp Destinations - _REQUIRES:_ [OpenWarp Dev Builds](https://github.com/Pneumaticraft/OpenWarp/wiki/)
## <a name="openwarp" href="#wiki-openwarp"></a>OpenWarp Destinations - _REQUIRES:_ [OpenWarp Dev Builds](https://github.com/Pneumaticraft/OpenWarp/wiki/)
`/mvtp ow:WarpName`
**Permissions**