Talk:Command
- Barrister
- Guppymomma
- Shagie (publically known info & minor formatting)
- Tyroney
- Undertow
- Yaten
1st comment
So how do we make this work well with the communication page, any ideas? --Guppymomma 25 July 2005 12:23 (PDT)
- "As well as the normal chat modes, you can also use commands in speech." --Ihope127 18:41, 8 August 2005 (PDT)
Command Redirect
It seems that the command pages (such as "/tell") are all automatically redirecting to a page without the "/" symbol in the title. This wouldn't normally be a problem, but the pages being redirected to have no text on them. Perhaps having the article redirected to or from the pages without "/"s would be a temporary fix.--Zyborg22 18:51, 27 October 2005 (PDT)
- This seems to be a recurring issue. I vote to move the articles to the non-slash names with the redirect on the slash names as we cannot be sure when any bug fixes will be done. --Guppymomma 19:41, 27 October 2005 (PDT)
- Agreed. --Barrister 00:36, 28 October 2005 (PDT)
- If I can manage to view the / pages, I'll move them to the non / names today since there've been no objections. --Guppymomma 09:20, 29 October 2005 (PDT)
- Okay those were insane. All moved. I think. Please check my work. I haven't fixed all the instances of the links. I'll do the template ones really fast, but that's all I have time for right now. --Guppymomma 22:26, 29 October 2005 (PDT)
- I think I may know why the command pages are redirecting to versions with no slash. When you put a slash before a word, it thinks you're trying to add that word to the current URL and/or simply doesn't see the "/" as part of the work. For example, a link to /this on this talk page will be sent to Talk:Command/this instead of an article called "/this".--Zyborg22 17:03, 31 October 2005 (PST)
- I don't think that's exactly it. While I was moving them to nonslash titles, half of them worked okay and the other half weren't. There was no specific pattern to which ones worked and which didn't that I could see. --Guppymomma 17:10, 31 October 2005 (PST)
- I think I may know why the command pages are redirecting to versions with no slash. When you put a slash before a word, it thinks you're trying to add that word to the current URL and/or simply doesn't see the "/" as part of the work. For example, a link to /this on this talk page will be sent to Talk:Command/this instead of an article called "/this".--Zyborg22 17:03, 31 October 2005 (PST)
- Okay those were insane. All moved. I think. Please check my work. I haven't fixed all the instances of the links. I'll do the template ones really fast, but that's all I have time for right now. --Guppymomma 22:26, 29 October 2005 (PDT)
- If I can manage to view the / pages, I'll move them to the non / names today since there've been no objections. --Guppymomma 09:20, 29 October 2005 (PDT)
- Agreed. --Barrister 00:36, 28 October 2005 (PDT)
wild cards? (when using "who")
Is there any kind of "wild card" character when searching via "/who" (or other related command; e.g. using "/vwho" when searching for a ship)? I'm specifically referring to when you know part of the name of the pirate (ship, crew, etc.) in question, and want to scan a list of matching names. Just wondering...Thanks. -- Franklincain (t/c) 20:13, 25 July 2012 (PDT)
OK, I see that "/cwho" (crew search) and "/fwho" (flag search) already have some wild-card capability. So that limits my question to pirates ("/who") and their ships ("/vwho"). -- Franklincain (t/c) 20:18, 25 July 2012 (PDT)
- No, /who and /vwho must be given exact names to check. Sorry Chupchup 20:31, 25 July 2012 (PDT)
Chat commands
/trade should probably go under the existing "Chat commands" heading. Chupchup 18:45, 4 April 2017 (UTC)
