So, the short version: I have multiple wow accounts linked to the same WTF folder in my WoW folder via junction links for the purpose of keeping my settings constant across all separate accounts.
The PROBLEM: If I have not logged into one of those accounts in a while, WoW will attempt to pull the last macros it remembers that account having, from its own server-- which overwrites my local macros. I do not want this as WoW is then overwriting current macros with older ones.
How do I force WoW to accept my local macros over the server-side ones?
2 Likes
Under your WTF folder each of your accounts will have itâs own folder with a name that is like â8145774#12â and each account folder should have itâs own macros.txt. Unless you are doing something weird with Windows and folder mappings that is unnecessary or using an add-on that syncs stuff across accounts (poorly), what you describe shouldnât happen. It also shouldnât delete the local macros.txt file unless you have problems with local permissions that prevent wow from reading the file originally.
This is what a Junction link is: https://www.computerhope.com/jargon/j/junction.htm
The way I have it setup: all of the folders like â8145774#12â filter into a single folder, and in this way, macros.txt is universal across all accounts.
Iâve actually had this issue for a long time now, and the way I have gotten around it in the past is to remove the write permission from EVERYONE on macros.txt, which will force WoW to accept my local copy instead of overwriting it with what it has on its servers. The downside is that I canât save anything written inside of WoW until I restore write permissionâŚ
The point at which it overwrites my local macros is during the character loading screen, when loading into the game world. Another work-around I have found is to leave macros.txt open in notepad and SPAM âSave As.â
I know there was a time when WoW did not sync macros at all, so I am figuring there is an âoffâ value somewhere.
Months ago (back in the old forum?) while helping someone else, a bunch of us figured out that WoW uses the local file (the macros.txt) as itâs primary copy and the version on the server as the backup. That way if you go to a new pc that youâve never installed wow on (and has no macros.txt), you wonât lose all your macros and it will it create a new macros.txt with the server version of the data. It also uses the server copy if there is a problem reading the file locally.
There is no way to turn that off.
I think the setup you have with junction files is causing the problem you now have. If your file permissions werenât a problem you wouldnât need to use junction files.
Focus on fixing the permissions issues.
- Make sure youâre logged in with an account that has admin rights to the whole drive
- Make sure wow and the bnet launcher was installed using this account.
- do not use a shortcut to run either wow or the bnet launcher as Administrator. That makes it run as a different user account and can contribute to the permissions issues.
- If youâre using the twitch desktop app, it has a handy feature for fixing file permissions and file associations that can help prevent problems later on.
1 Like
I appreciate the input, but I am not certain you understand. Without the junction links, I would have a macros-cache.txt file for â51474193#1â and a completely separate macros-cache.txt for â95100047#1â and another separate file for â95100047#2â and so onâŚ
Now you say that the game prioritizes the local copy instead of the server copy? In my experience it has been the opposite. Even on my laptop, a completely different system without junction links, I have had the same problem; the game will overwrite my macros with a server-side copy that is outdated.
/run SetCVar('synchronizeMacros', 0)
https://wow.gamepedia.com/CVar_synchronizeMacros
5 Likes
Thanks for that. I knew there had to be a simple on or off switch!
For me, nothing worked, I tried all four variables:
/run SetCVar(âsynchronizeConfigâ, 0)
/run SetCVar(âsynchronizeMacrosâ, 0)
/run SetCVar(âsynchronizeBindingsâ, 0)
/run SetCVar(âsynchronizeSettingsâ, 0)
But it still overwrote my general macros. So I found a workaround:
- Copy your backed-up macros, bindings, settings, and config files into your game folders.
- Launch the game, it will still overwrite them as usual.
- Now hereâs the trick: delete all the macros on the general tab, then log out to the character selection screen but donât close the game.
- While at the character screen, overwrite the files again with your backups.
- Then log in, this time, the game should load your files correctly and not overwrite them.
- Once everything looks right, log out again, then close the game, and back up the working files once more.
Whenever things get messed up again, just restore your backups or repeat the process as needed.
Not sure why Blizzard doesnât honor a simple âdonât replace my filesâ rule, but at least this workaround does the job.