Inconsistent subcommand descriptions in hotbar-related text commands

There are four hotbar-related text commands which set actions.
/hotbar

Quote:

---

>>Subcommands
action "action name" [#1] [#2]

---

/pvphotbar

Quote:

---

>>Subcommands
action "action name" [#1] [#2]

---

/crosshotbar

Quote:

---

>>Subcommands
set "action name" [number] [slot name]

---

/pvpcrosshotbar

Quote:

---

>>Subcommands
set "action name" [number] [slot name]

---

In the English version, "action" is used in the description of hotbar, while "set" is used in the description of crosshotbar. In fact, both "action" and "set" are accepted as valid subcommands in all of these text commands.

In the Japanese version, "set(action)" is used consistently instead of "action" or "set" in the descriptions of these text commands. I believe that "action" and "set" should be replaced with "set(action)".

Additionally, "PvP action name" is used instead of "action name" in the descriptions of /pvphotbar and /pvpcrosshotbar. I believe this wording is more appropriate.

Are you suggesting that they should say, for example

Quote:

---

Originally Posted by /? hotbar

>>Subcommands
set(action) "action name" [#1] [#2]

---

I do not support this suggestion, as people will take it literally and try to do

/hotbar set(action)

It is sufficient to list just "action" or just "set" and let the other be a secret alias.

Yes, your interpretation is correct. I hadn't considered the possibility of it being interpreted that way. Thank you for pointing it out.

This kind of notation is often used in other language versions. For example, "set(action)" is rendered as "placer (set)" in the French version and "legen (set)" in the German version (there is no space before the left bracket in the Japanese version, but there is in the German and French versions). However, I found only a few such examples in the English version, so I can see your point.

Quote:

---

/magiaauto [subcommand]
[...]
>>Subcommands:
　attack (atk)

---

I believe confusion is unlikely since there is a separate explanation for the example:

Quote:

---

>>Examples:
　/hotbar action "Mount Roulette" 1 1
　(Places Mount Roulette in slot [#1] on hotbar [#1].)

---

However, I have no strong preference regarding listing both subcommands in this manner, so I’m happy to leave it to the l10n team's decision.