Nbsami wrote:I just discovered that I can't bind commands anymore. When I type "bind", it comes up with this wonky error:
That's not an error, but a complete(?) listing of all the options you can use when you want to bind a key to an action or event.
'help bind
Help about 'bind'
Syntax:
bind [-nfreg] <command>
Flags (default -nrf):
n - used in normal-mode
f - used in fire-mode
r - used in run-mode
e - leave command in line edit
g - global key (not recommended)
Multiple commands can be bound to the same key be seperating them with semicolons.
Special bind's:
bind commandkey - sets commandkey
bind firekey1 - sets first firekey
bind firekey2 - sets second firekey
bind runkey1 - sets first runkey
bind runkey2 - sets second runkey
Examples:
bind -f cast paralyzed (F3)
will typically mean that Shift-F3
is used to select that spell (Shift
being the fire key)
bind use_skill sense curse;
use_skill sense magic (S)
will bind those two commands to the S key.
FWIW, a common binding that I have is binding the praying skill to the "p" key
Using an out of date client/server may also be a source of such problems. Try updating to latest stable release (or even to CVS, althouh then you'd have to ask Ryo nicely) and see if it works better.
i had a memory leak with 1.7.0/1.7.0, fixed with 1.7.0/1.7.1 and i always have my old chars (even from 1.6.0 server)... so you don't need to create a new one if you keep your [etc/]crossfire directory
changing client don't change server saved files
