Basically inverse of their counterpart functions.

For instance:

/alias test "echo moo"
/test
moo
/unalias test
/test
Error: no such command 'test'

Certainly, there are more important things to take care of first, but, in terms of general suggestions, this is something I would like to see :-P Thanks :)

<edit>
Add 'unset' to this list too :-P
</edit>

--
kihjin

Just a quick note that you can unbind keys by binding them to '' (two empty single quotes). Also, you can remove aliases by deleting them from the wgaf.cfg file when VO isn't running; but I would also like to see an unalias command for in-game removal.

Personally, I'd like a command that loads the contents of a file into memory, but not into wgaf.cfg. That way I could do, like /eload "testlayout.cfg" and use a new keyboard layout without having the contents of testlayout.cfg copied into my wgaf.cfg file for all eternity.

PS: I do know I can get this behavior by killall-ing Vendetta, or any other method of force quitting it. However, I would like it ingtegrated into the game. :D

Rog, that's probably not very easy to do since everything in memory is just copied to the wagf file when you properly exit. To implement your suggestion the client would have to add information with ever single bind, alias and set command as to wether or not it should be written to the wagf file, and if it shouldn't then what command should be in its place. That's a number of man hours for such a small dev team.

Instead I'd suggest that you just make copy of your current wagf file and "default.cfg" and when you're done using "testlayout.cfg" load the original "default.cfg". You'll still have the extra aliases in your "wagf.cfg" file but they wouldn't be bound to any of the keys that you normally have bound.

That's something I'd like to see as well. I thought that was what it already did, until I tried it myself and noticed the wgaf.cfg file filling up with random testing aliases I had made.

Wouldn't it be just as simple as adding a boolean element to the bind/alias structure? Assuming each bind/alias is a structure like the following:

bind {
char key;
string cmd;
bool perm; // whether to store in wgaf
}

alias {
string name;
string cmd;
bool perm;
}

Then, depending on how the alias/bind is set, either from an 'eload' or 'load', or, from wgaf directory, or from the command line, when the client exits properly:

if(perm)
write(wgaffd, ...)

Then again, it all depends on how VO is setup internally. It wouldn't be something that would take 1 minute to implement of course. Nevertheless, would be cool :-P

--
kihjin

kihjin, in addition to adding that bit, they'd also have to change all the necessary functions to check the bit. It's not a huge amount of time but I'm sure it's over an hour given the amount of code that is involved in something the size of Vendetta, more on point there are probably only 10 of us (I'd be one of them) that would actually use it.

Thats true :(

Oh well. Shucks!

--
kihjin