Page 1 of 1

Compatibility with new character-specific keybindings?

Posted: Mon Nov 04, 2013 2:51 am
by SilverNexus
I updated my trunk client to the newest version (r19093), which has the character-specific keybindings as a feature.
When I logged into Metalforge with the new client, absolutely no keybindings work (not even the default ones). Any keybindings I try to create go to a (null).keys file and do not persist to another login.
When I log into netarbeiter (1.70.0), my keybindings work fine.

Does this mean the newest trunk client is incompatible with the 1.12 branch? Or am I doing something wrong?

Re: Compatibility with new character-specific keybindings?

Posted: Mon Nov 04, 2013 11:46 pm
by Leaf
SilverNexus wrote: Does this mean the newest trunk client is incompatible with the 1.12 branch? Or am I doing something wrong?
For the moment, assume yes until further testing is complete.

Posted: Tue Nov 05, 2013 1:16 am
by Leaf
Yes, a known problem.

Patch has been submitted & waiting for review before applied to the trunk code base.

source:
http://mailman.metalforge.org/pipermail ... 13254.html

Posted: Tue Nov 05, 2013 2:46 am
by SilverNexus
Okay. Good to know it will be fixed shortly.

I was beginning to worry I'd have to use a separate client to play on the metalforge server.

Posted: Wed Nov 06, 2013 12:40 am
by Leaf
Fix is in place. Make sure to update your client to r19095 and then recompile.

Some of the changes have to do with:

* Per character keybindings file
* Only bind lowercase keys
* All keybindings are shown by default in the keybinding editor
* Bug fixes in regards to keybinding with alt, control, and shift keys

You may have to rebind some|many|all your existing keybindings after updating - depending how they were initially configured.

Posted: Thu Nov 07, 2013 11:01 pm
by SilverNexus
Seems to work beautifully. :D

Posted: Mon Nov 11, 2013 8:54 pm
by Leaf
Good to hear and thank you for the update.