You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 3, 2022. It is now read-only.
What are you trying to do?
I want to have warps that have spaces in them and/or special characters.
For example: helm's deep
Currently only alphanumeric values are supported.
Ideally this would be the default behavior instead of having to type /warp "helm's deep"
Describe the solution you'd like
Add the ability for special characters and spaces in warps.
Describe alternatives you've considered
Make users use quotations.
Create warps without spaces.
Used a different essentials plugin - Bedrock that we've modified to support this ability.
Anything else that might help?
Warps with special characters are currently supported in the warp list command and you can click those warps to get to them. This just does not work when typing a warp <warp> command.
The text was updated successfully, but these errors were encountered:
Freshmilkymilk
changed the title
Allow for spaces and special characters in warps
Allow for spaces and special characters in warps by default
Jan 27, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What are you trying to do?
I want to have warps that have spaces in them and/or special characters.
For example:
helm's deep
Currently only alphanumeric values are supported.
Ideally this would be the default behavior instead of having to type
/warp "helm's deep"
Describe the solution you'd like
Add the ability for special characters and spaces in warps.
Describe alternatives you've considered
Anything else that might help?
Warps with special characters are currently supported in the
warp list
command and you can click those warps to get to them. This just does not work when typing awarp <warp>
command.Here's the issue for that fix: #747
The text was updated successfully, but these errors were encountered: