Many of these already have names in the mainspace that could use expansion, rather than second pages. Ie, Friend (keep it there please!). May want to have a look and then change the links on this page to match. --Sky (t · c · w) 23:54, 31 December 2008 (UTC)
- The Friend page deals specifically with the generalized term Friend, what it means, etc... What I'm creating is pages dealing with the command /friend. All of the macro commands here are grouped together in a format like the WoW API, and I intend to add this to the Holy Writ section of the UI portal. The distinction is clear enough between Friend and /friend, and the format of the Macro API pages needs to be standardized. I would not mind putting links to these commands on pages that exist, but creating the Macro API is enough work as it is, and I don't really feel the need to go hunt down all of these commands to place links on pages that already exist in a more general sense. --DrDoom (talk) 21:37, 1 January 2009 (UTC)
I removed this section as it does not pertain to all macros. Some macros already have the conditionals included (see MACRO cast. If you would like to improve that part, maybe a better way would be to make that section a link to another page that you can click on via the argument list, then you can add it to all of the macros for which conditionals work. You could add a subsection regarding conditionals, or maybe just as a note at the bottom, and link to it, but make sure it is specified that not all macros support conditionals. Only certain macros will process these. Thanks for wanting to make this a better place, but we just need to keep it in a manner that keeps things clear and concise to everyone. If you have any questions about adding major information, please post here for group discussion. --DrDoom (talk) 00:34, 17 January 2009 (UTC)
- Ok, thanks for the help. I have no idea which commands conditionals work for so I guess I'll just leave it alone. -Cowlinator (talk) 01:20, 17 January 2009 (UTC)
I suppose some people find the title "Macro API" to be inappropriate for this section, and I see it has already been renamed on the main UI portal page. Here are the reasons why I chose to name it as an API rather than just "commands":
- It follows the same page format as API pages
- These commands are literally functions, and deserve to be treated as such. They are passed arguments and each one performs a specific task, just like the LUA functions. The fact that they are called via the command line or a Macro shouldn't have any bearing on this.
- API stands for Application Programming Interface, and Macro Commands are sometimes a necessary part of scripting, as there are things you can do in a macro command that is not possible (in combat) with LUA scripting.
- There are a million iterations of "Macro Commands" pages out there, many of them being on wowwiki as well. I wanted to make sure that anyone viewing it realized that this should be one of the first places to look to see correct syntax and usage of any macro commands they intend to use. EDIT: To clarify, I mean to distinguish it from a Guide page, as it is not intended to be a guide to instruct people on how to do various tasks; only to list syntax and functionality.
Music Player Commands
I noticed that the Music Player Commands section is empty with red links. I'm planning on testing the commands and playing with them a bit, and will come back with the results (Patch 3.1.0 is taking forever to download). I'm not planning on making pages for said commands, but I will if need be. --DJ 1337 Man (talk) 23:28, 14 April 2009 (UTC)
- Hey thanks for the help, but after reviewing the output again with the 3.1.0 data, I discovered that these were not commands, but instead arguments to the /stopwatch command. The global variables start with SLASH_ like all other commands, but the value is not preceded by a "/". Its a little odd to me but hey it works for them I suppose. That section has been removed and the /stopwatch command updated. --DrDoom (talk) 11:39, 15 April 2009 (UTC)
Merge with List of slash commands?
Since someone suggested we merge this with slash commands and did not post anything here, I guess I'll start it up. I don't see much difference in the two, save for the page referred to is pretty incomplete and out of date. I will add the emotes to this page, though, and I vote that the other page be set up to redirect to or reference this page. --DrDoom (talk) 23:35, June 3, 2010 (UTC)
- This makes sense to me. All slash commands redirects to the referenced page as well. I'd say there's quite a bit of overlap on Slash commands that could be cleaned up as well. Two thirds of that page are just categorized emotes. Elviswind (talk) 01:26, June 22, 2010 (UTC)
The reason for leaving a seperate page is that the Macro "API" or "Reference" is a far larger topic than just the list of /commands. Having a root topic for a major functional portion of UI Customization is conducive to allowing that topic to grow and be manageableover the long term. Removin the suggestion for now, these are beign reworked. Celess (talk) 22:43, August 3, 2012 (UTC)
It states on the page that /mountspecial doesn't do anything. This is inaccurate.
mountspecial makes your currently mounted mount do it's "special" action. This can also be triggered by using the up button when you are on a ground mount or on a flying mount in a no-fly zone. This is useful when you want to make a flying mount (for instance a drake) do it's special action (for instance roar), when you are in a flying zone, and the jump/up button would make you start flying instead of triggering mountspecial.
Special actions vary from mount to mount. Most are simple grunts and roars. Most have a sound as well as an animation. Some are more unique, like the Sea Turtle, who will pop into (and back out of) his shell with a cartoony sound. Some mounts don't do anything.
So, while it doesn't do anything if one is unmounted, it is inaccurate to state that it does nothing in general.
Maybe the * descriptor should be changed to "only works when mounted." The item "unused" would then be the only one that "does nothing."