Does alt language character on other DC get their own HUD layout+macros ?

[aereniil]

Hi,

I've been planning for a long time to create a new alt character on a different Data Centre so I can enjoy the entire FFXIV experience again, this time in a different language and from a new perspective (at a slower, more thorough pace, and so on).

I want to change the entire game language (not just the story and cutscenes), while still being able to switch back to my main "English-set" character whenever I want by restarting the game in English.

However, when I tried changing the game language and logged in with my main account, I noticed that all my macros broke because job names and ability names differ between languages (for example, when using \micon ...).

So before I start this new project:
Do different characters on different Data Centres share the same macros and HUD layouts, or can I customize them separately for each character?

Thank you in advance for any help!

[Mikoko_Miko]

There are some exceptions, but in most cases you can make macros work in other languages by using the auto-translate function. It is important to use auto-translate (or Tab-key auto-completion) for both the command and its arguments, including job names and action names. Some subcommands, such as on/off, current/share, or placeholders, are not auto-translate ready, yet they are recognised as valid across different language versions. There are about 200 macros in my macro editor, and almost all of them work across all client languages without any problems. But if you toggle HUD layout using a macro, it may not work in another language settings since the arguments of /hud command depends on client language. Enemysigns and Quickchats may also cause problems, but you can resolve this by including multiple language-specific lines within a single macro.

[aereniil]

There are some exceptions, but in most cases you can make macros work in other languages by using the auto-translate function. It is important to use auto-translate (or Tab-key auto-completion) for both the command and its arguments, including job names and action names. Some subcommands, such as on/off, current/share, or placeholders, are not auto-translate ready, yet they are recognised as valid across different language versions. There are about 200 macros in my macro editor, and almost all of them work across all client languages without any problems. But if you toggle HUD layout using a macro, it may not work in another language settings since the arguments of /hud command depends on client language. Enemysigns and Quickchats may also cause problems, but you can resolve this by including multiple language-specific lines within a single macro.

Thank you very much ! Very smart ideas/workarounds, indeed. Then, I will try to adapt my macros and test them, before going any further.

[Mikoko_Miko]

I forgot to include a note, so I'm adding it here. Some auto-translation entries use identical English terms, but their equivalents differ in other language versions. For example, {follow}/{Follow} is used across four separate categories:
Transportation (to follow someone as you walk)
Communication (to follow someone's blog)
Companion Actions (to order the chocobo to follow you)
Pet Actions (to order the faerie to follow you)
And when used in macros, these do not work in other languages.

I encountered the same issue with {Guardian} (PvE action, PvP action, and Eorzean gods) and {Guard} (Pet action and PvP action). In these cases, you must press Tab with nothing typed before the cursor, choose the category first, and then choose the term (or change the client language first, then enter the term). Good luck.