Keybinds???

[abeiron]

Is there not way to prevent them from erasing? i have different binds with different characters and it messes me up big time to have to remember every different character specific bind. Any solutions would be appreciated thanks

[Kemii]

click the button that says "character specific binds"

[nerosm]

/console synchronizeBindings 0

[Kite009]

First of all, make backup of your WTF folder. Bind keys as you like in your toon in-game with character-specific keybinds on, then exit wow. Go to WTF>Account>YourAccount>Frostwolf>YourCharacter. There should be files named bindings-cache.wtf and bindings-cache.old (second one may not be present for some toons). For both these files, ENABLE read-only.

You may have to repeat this for all alts you have, and once you enable read-only for a toon, any keybind changes for that toon will not be saved, unless ofcourse you revert the attribute.

[bornaa82]

First of all, make backup of your WTF folder. Bind keys as you like in your toon in-game with character-specific keybinds on, then exit wow. Go to WTF>Account>YourAccount>Frostwolf>YourCharacter. There should be files named bindings-cache.wtf and bindings-cache.old (second one may not be present for some toons). For both these files, ENABLE read-only.

You may have to repeat this for all alts you have, and once you enable read-only for a toon, any keybind changes for that toon will not be saved, unless ofcourse you revert the attribute.

works. this is a first real permanent fix for this annoying bug..thanx!

[Qweerty]

First of all, make backup of your WTF folder. Bind keys as you like in your toon in-game with character-specific keybinds on, then exit wow. Go to WTF>Account>YourAccount>Frostwolf>YourCharacter. There should be files named bindings-cache.wtf and bindings-cache.old (second one may not be present for some toons). For both these files, ENABLE read-only.

You may have to repeat this for all alts you have, and once you enable read-only for a toon, any keybind changes for that toon will not be saved, unless ofcourse you revert the attribute.

where should i enable that read-only?

[Arpeggio07]

where should i enable that read-only?

Right click > properties

[TMVN]

Anyone know if this bug has been fixed with the last update?

[BenitoWBAT]

Anyone know if this bug has been fixed with the last update?

it wasnt
msg too short

[CrazyCaptcha]

First of all, make backup of your WTF folder. Bind keys as you like in your toon in-game with character-specific keybinds on, then exit wow. Go to WTF>Account>YourAccount>Frostwolf>YourCharacter. There should be files named bindings-cache.wtf and bindings-cache.old (second one may not be present for some toons). For both these files, ENABLE read-only.

You may have to repeat this for all alts you have, and once you enable read-only for a toon, any keybind changes for that toon will not be saved, unless ofcourse you revert the attribute.

This is my temporary fix about it: Just open "bindings-cache.wtf" with notepad and write there the keybinds.. like this..

For this just make backup files too.

BINDINGMODE 1
bind Q STRAFELEFT
bind E STRAFERIGHT
bind NUMPADDIVIDE NONE
bind R MULTIACTIONBAR1BUTTON1
bind - ACTIONBUTTON11
bind = NONE
bind CTRL-F1 NONE
bind CTRL-F2 NONE
bind CTRL-F3 NONE
bind CTRL-F4 NONE
bind CTRL-F5 NONE
bind G MULTIACTIONBAR1BUTTON4
bind F MULTIACTIONBAR1BUTTON3
bind T MULTIACTIONBAR1BUTTON2
bind SHIFT-T MULTIACTIONBAR1BUTTON7
bind SHIFT-G MULTIACTIONBAR1BUTTON8
bind . ACTIONBUTTON12
bind , TOGGLERUN
bind } ARH_TOGGLEYELLOW
bind { ARH_TOGGLEGREEN
bind + ARH_TOGGLEHUD
bind < NONE
bind ñ NONE
bind SHIFT-W MULTIACTIONBAR1BUTTON6
bind | MULTIACTIONBAR1BUTTON5
bind SHIFT-Q MULTIACTIONBAR1BUTTON9
bind SHIFT-F MULTIACTIONBAR1BUTTON10
bind SHIFT-E MULTIACTIONBAR1BUTTON11
bind SHIFT-R MULTIACTIONBAR1BUTTON12
modifiedclick CTRL FOCUSCAST
modifiedclick ALT AUTOLOOTTOGGLE

And save it as "bindings-cache.wtf" on main WOW files. Then just change name of the bindings-cache.wtf from accounts and copy and paste the new one.. ALL WITH CLOSED GAME.


Then enter and see whats happens.



You will do this everytime you want to open the client.

This is a temporary fix.. We should wait for development fix issues.


Good luck.