>> There are several client commands that aren't documented. Technically this >> is a server issue. Someone should take a few minutes and compare with >> output of 'help commands' with the list of commands in the source. Then >> help text should be added for any command that doesn't have it. This is >> boring, but really necessary for the 1.0 release. > > Note that there are lots of commands listed which are really no worthy of > documentation or should not be shown to the player. > > For example, there is no reason most people should care about the archs, logs, > malloc, sstable, strings, and time. > > There are many others which are pretty self documenting (direction commands, or > ones that are already bound to keys and people pretty clearly know what they > mean.) > > The biggest issue might be that the 'help commands' shows all these other > commands, many of which are really debugging commands, but not really harmful > for other people to run. So what we should have: 'help commands: Commands: apply brace cast disarm dm drop dropall east examine fire fire_stop fix_me get gsay help hiscore inventory invoke listen mapinfo maps mark motd north northeast northwest output-count output-sync party peaceful pickup players prepare quit ready_skill resistances rotateshoottype rotatespells run run_stop save say search search-items shout shutdown skills sound south southeast southwest statistics stay take tell throw title use_skill usekeys version west who wimpy Debugging commands: archs logs malloc sstable strings time verify If this is dynamically generated from Commands[] in commands.c, then it's leaving out NewServerCommands[]. Also: No help availble on 'brace' No help availble on 'disarm' No help availble on 'dm' No help availble on 'drop' No help availble on 'dropall' ... It should be easy enough to add a brief message for each command. --PC