Currently, for me, 30 is enough but I wouldn\'t mind seeing more shortcut slots available.
I can imagine a PS installation shared by more than one person, where, each player wants his own settings, including his own shortcuts and keys.
So, unless psclient starts keeping player settings on a *per player* way as opposed to the current global way, I see the usefullness of more (at least) shortcut slots so there\'s plenty for each player favorite shortcut definitions.
One quick \"dirty\" external hack would be to start psclient through a batch/script file that would accept a $player arg doing something like:
1) copy from ./PlayerSettings/${player}/data/options/*.xml to ./data/options/
2) start psclient
3) copy all ./data/options/* back to ./PlayerSettings/${player}/data/options/
I already tested this on one of my PCs and it works
I\'ve included the ./planeshift.cfg file and made it so it only keeps track of some but not all *.xml files. Only the usefull to be kept \"per player\" letting the others stay as \"global\".
It\'s not a nice solution though, but it works if one needs such a setup.
It would be nice to see in the future an \"official\" solution for multi per-player settings on such things as keyboard mapping, shortcuts definitions and window state/size/positions, etc...
errr... btw, since I\'m touching this subject :>
I miss $vars on shortcut definitions. So something like /target $me would be possible.
If no $vars are planned, then at least a /target_me or equivalent command would be nice.
This would let me do a more general version of:
/target Koshdukai; /cast defensive wind; /target_nearest_next_npc
with something like:
x=$target; /target $me; /cast defensive wind; /target $x
*or*
/target_me; /cast defensive wind; /target_previous (if any)
hmmm... one other usefull addition would be an /alias system (as in *nix shell) but the shortcut slots are an already usefull resource anyway.
*phew*... enough almost-off-topic for now ;P
