Thank you very much ! Very smart ideas/workarounds, indeed. Then, I will try to adapt my macros and test them, before going any further.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.
Last edited by aereniil; Yesterday at 02:42 AM.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.


Reply With Quote

