Skip to content
toadbomb edited this page Mar 22, 2012 · 1 revision

In order to properly understand this command reference, there are a few things you need to know:

Variables

Items written in uppercase should be replaced with a variable. Items in lowercase should be typed exactly as shown.

Required vs. Optional Parameters

Items inside angled brackets (<>) are REQUIRED parameters, and must be supplied in the order they are shown. Items inside square brackets ([]) are optional parameters, and can be supplied in any order, but they must come after the required parameters.

Back to Top

If [NAME] is provided, warps the player to the selected QT. If economy is enabled and Vault is installed, charges the player accordingly. If [NAME] is not provided, returns a list of QTs the player can warp to from their location, if any.

Usage:

/qt [NAME]

Examples:

/qt my_warp
/qt

Permission:

qt.user

Back to Top


Creates a new QT named <NAME> at your current location. Names must contain letters, and cannot contain spaces or match QuickTravel commands, however they can contain numbers.

Usage:

/qt create <NAME> [-r RADIUS] [-e [true|false]] [-f [true|false]] [-d [true|false]] [-p [true|false]] [-m [true|false]]

Optional parameters:

  • [-r/-radius RADIUS] : Sets the radius size for this QT.
  • [-e/-enable/-enabled [true|false]] : Sets whether this QT is enabled. If [true|false] is not provided, it chooses the opposite of the setting enabled-by-default in your config.yml.
  • [-f/-free [true|false]] : Sets whether all travel to/from this QT is free, overriding all other settings. If [true|false] is not provided, it chooses the opposite of the setting free-by-default in your config.yml.
  • [-d/-disc/-discover/-discovery [true|false]] : Sets whether players need to discover this QT before they can warp to it. If [true|false] is not provided, it chooses the opposite of the setting require-discovery-by-default in your config.yml.
  • [-p/-perm/-perms [true|false]] : Sets whether permissions are required to use/discover/warp to this QT. If [true|false] is not provided, it chooses the opposite of the setting require-permissions-by-default in your config.yml.
  • [-m/-multi/-multiworld [true|false]] : Sets whether this QT is multiworld or not. If [true|false] is not provided, it chooses the opposite of the setting multiworld-by-default in your config.yml.

Examples:

/qt create my_warp
/qt create warp1 -p -f -d -e true
/qt create warp2 -d -r 5.5
/qt create warp3 -r 12 -e -d true -p false -m

Permission:

qt.admin.create

Back to Top


Renames the QT <NAME> to <NEW NAME>. Names must contain letters, and cannot contain spaces or match QuickTravel commands, however they can contain numbers.

Usage:

/qt rename <NAME> <NEW NAME>

Examples:

/qt rename warp2 warp6
/qt rename warp3 Warp3

Alias:

/qt name

Permission:

qt.admin.rename

Back to Top


Sets the type of the QT. In the case of [toggle], it will toggle between radius or cuboid. If only <NAME> is provided, returns the type. If <*> is provided instead of <NAME>, it will run the operation on ALL currently created QTs.

Usage:

/qt type <NAME|*> [radius|cuboid|toggle] [-w WORLD]

Optional parameters:

  • [-w WORLD] : If <*> is provided instead of <NAME>, only affects QTs in world [WORLD].

Examples:

/qt type my_warp
/qt type warp2 cuboid
/qt type * toggle
/qt type * -w world_nether radius

Alias:

/qt t

Permission:

qt.admin.type

Back to Top


Changes the type of QT <NAME> to radius. If <*> is provided instead of <NAME>, it will run the operation on ALL currently created QTs.

Usage:

/qt radius <NAME|*> [-s SIZE|reset] [-w WORLD]

Optional parameters:

  • [-s SIZE|reset] : Sets the QT's radius to [SIZE]. In the case of [reset], returns the size of the radius to the default setting as set in your config.yml.
  • [-w WORLD] : If <*> is provided instead of <NAME>, only affects QTs in world [WORLD].

Examples:

/qt radius warp1
/qt radius *
/qt radius warp2 -s 12
/qt radius * -s reset -w world_the_end

Alias:

/qt r

Permission:

qt.admin.radius

Back to Top


Changes the type of QT <NAME> to cuboid. If <*> is provided instead of <NAME>, it will run the operation on ALL currently created QTs, and will ignore optional parameters [-a] or [-b].

Usage:

/qt cuboid <NAME|*> [-a] [-b] [-w WORLD]

Optional parameters:

  • [-a] : Sets the primary coord for the cuboid shape of QT <NAME> to your current location. NOTE: Cannot be used in conjunction with <*> or [-b].
  • [-b] : Sets the secondary coord for the cuboid shape of QT <NAME> to your current location. NOTE: Cannot be used in conjunction with <*> or [-a].
  • [-w WORLD] : If <*> is provided instead of <NAME>, only affects QTs in world [WORLD].

Examples:

/qt cuboid warp1
/qt cuboid * -w world
/qt cuboid warp2 -a
/qt cuboid warp2 -b

Alias:

/qt c

Permission:

qt.admin.cuboid

Back to Top


Moves the selected radius QT to your current location.

Usage:

/qt move <NAME>

Example:

/qt move warp1

Permission:

qt.admin.move

Back to Top


Sets the arrival spot for the selected QT to your current location.

Usage:

/qt dest <NAME>

Example:

/qt dest warp2

Permission:

qt.admin.dest

Back to Top


Enables the QT <NAME>. If <*> is provided instead of <NAME>, it will run the operation on ALL currently created QTs.

Usage:

/qt enable <NAME|*>

Optional parameters:

  • [-s true|false|toggle] : Sets whether the QT is enabled or not to the given state. In the case of [toggle], toggles between whether the QT is enabled or not.
  • [-w WORLD] : If <*> is provided instead of <NAME>, only affects QTs in world [WORLD].

Examples:

/qt enable my_warp
/qt enable * -s false -w world_nether
/qt enable * -s toggle

Alias:

/qt e

Permission:

qt.admin.enable

Back to Top


Disables the QT <NAME>. If <*> is provided instead of <NAME>, it will run the operation on ALL currently created QTs.

Usage:

/qt disable <NAME|*>

Optional parameters:

  • [-s true|false|toggle] : Sets whether the QT is disabled or not to the given state. In the case of [toggle], toggles between whether the QT is enabled or not.
  • [-w WORLD] : If <*> is provided instead of <NAME>, only affects QTs in world [WORLD].

Examples:

/qt disable my_warp
/qt disable * -w world_nether
/qt disable * -s toggle -w world

Permission:

qt.admin.disable

Back to Top


Sets the price to warp from QT <A> to QT <B> at <PRICE>. If <reset> is given instead of <PRICE>, QuickTravel will calculate the price for you based on distance.

Usage:

/qt price <A> <B> <PRICE|reset>

Examples:

/qt price my_warp warp2 300
/qt price warp2 warp1 reset

Alias:

/qt charge

Permission:

qt.admin.price

Back to Top


Sets whether all travel to/from the QT <NAME> is free. In the case of <toggle>, it will toggle between whether travel is free or not. If <*> is provided instead of <NAME>, it will set whether travel is free for ALL currently created QTs. NOTE: Overrides all other settings.

Usage:

/qt free <NAME|*> <true|false|toggle>

Optional parameters:

  • [-w WORLD] : If <*> is provided instead of <NAME>, only affects QTs in world [WORLD].

Examples:

/qt free my_warp true
/qt free * false
/qt free * toggle -w world

Alias:

/qt f

Permission:

qt.admin.free

Back to Top


Sets whether the QT <NAME> needs to be discovered before it can be travelled to. In the case of <toggle>, it will toggle between whether discovery is required or not. If <*> is provided instead of <NAME>, it will set whether travel is free for ALL currently created QTs. NOTE: Overrides the require-discovery-by-default option in your config.yml.

Usage:

/qt discovery <NAME|*> <true|false|toggle>

Optional parameters:

  • [-w WORLD] : If <*> is provided instead of <NAME>, only affects QTs in world [WORLD].

Examples:

/qt discovery my_warp true
/qt discovery * false
/qt discovery * toggle -w world

Aliases:

/qt d
/qt disc
/qt discover

Permission:

qt.admin.discovery

Back to Top


Sets whether permissions are required to use/discover the QT <NAME>. In the case of <toggle>, it will toggle between whether permissions are required or not. If <*> is provided instead of <NAME>, it will set whether travel is free for ALL currently created QTs. NOTE: Overrides the permissions-required-by-default option in your config.yml.

Usage:

/qt perms <NAME|*> <true|false|toggle>

Optional parameters:

  • [-w WORLD] : If <*> is provided instead of <NAME>, only affects QTs in world [WORLD].

Examples:

/qt perms my_warp true
/qt perms * false
/qt perms * toggle -w world

Aliases:

/qt p
/qt perm

Permission:

qt.admin.perms

Back to Top


Sets whether the QT <NAME> is multiworld or not. In the case of <toggle>, it will toggle between whether the QT is multiworld or not. If <*> is provided instead of <NAME>, it will set whether travel is free for ALL currently created QTs. NOTE: Overrides the multiworld-by-default option in your config.yml.

Usage:

/qt multiworld <NAME|*> <true|false|toggle>

Optional parameters:

  • [-w WORLD] : If <*> is provided instead of <NAME>, only affects QTs in world [WORLD].

Examples:

/qt multiworld my_warp true
/qt multiworld * false
/qt multiworld * toggle -w world

Aliases:

/qt m
/qt multi

Permission:

qt.admin.multiworld

Back to Top


Displays a list of ALL QTs regardless of whether they are enabled or not, what world they are in, whether the player has discovered them, etc. Also displays status info for each QT listed.

Usage:

/qt list [PAGE]

Examples:

/qt list
/qt list 3

Permission:

qt.admin.list

Back to Top