Crossfire Forum

Based of a discussion on cf-devel, where should keybindings be stored?

client, based on character name
client, for all characters
server, based on character name
seperate file that can be easily accessed, copied and edited
some combination of the ones mentioned above

I'm looking for suggestions or clarifictions before creating a poll.

Reference:
http://archives.real-time.com/pipermail ... 04661.html

What about something like mixing client/server?
For instance: client uses local bindings.
But you can 'upload' that (small) file (and only key bindings!) to the server with a short name.
Now you could store different bindings on the server (based on name), so different computers could use those. On the other hand you could also restore bindings on a new CF computer from server, and then adjust'em according to keyboard.

I think the combination of both server & player name is great for local at least. Since you can have players named the same way on different servers, or different players (with different playing strategies) on the same server.

I realy dont care if the bindings are on the client or server side, just as long as they are stored on a per charactor basis.

Clientside. One file for global keybindings and separate files for server/player.

otoh, if the spells were in some kind of popup window that could be accessed easily there wouldn't be any need for such system, would there?

seperate file that can be easily accessed, copied and edited

hoxu wrote:Clientside. One file for global keybindings and separate files for server/player.

I agree to this. You should be able to define hotkeys for you spells depending on your character (a high-level wizard uses different spells than a new hero, think for example of burnig hands versus dragonbreath). On the other hand I'd like to be able to define some basic key structure for every character (like a general identify button, which I am using).

Clientside. Not bound to a specific character, but instead manually selectable by the user (either by a dialog window, or simply by commands like "/keyload <file> /keysave <file>")