New wiki-style database of Smaug commands

Further to the ideas raised here:

http://www.gammon.com.au/forum/bbshowpost.php?bbsubject_id=6665

This forum now has a section devoted to being a database of all SMAUG commands. This is in the section of the forum:

http://www.gammon.com.au/forum/bbshowpost.php?bbtopic_id=115


You can go directly to a particular command by using the '?wiki=command' URL format, like this:

http://www.gammon.com.au/forum/bbshowpost.php?wiki=look


I will shortly be generating an "index" page to group commands into related categories, as far as possible.

Anyone who is familiar with administering Smaug is welcome to edit any of the posts in the command section and add their thoughts.

This section of the forum is designed as "wiki-style" which means that any user can edit any of the posts in it. Thus, you simply edit an existing post, add further explanatory notes, and then save your changes.

---

The entries in the Commands section of the forum have been automatically generated by:

• Parsing the commands.dat file to obtain a complete list of commands that can be entered
  
• Parsing the help file (help.are) to obtain a list of all help topics
  
• Generating one page per command listing the information from commands.dat (eg. minimum level, minimum position) and then following that by the help topic for that command, if any.

The index of all commands (sorted into alphabetic order within level order) is at:

http://www.gammon.com.au/forum/bbshowpost.php?wiki=index

This is great, Nick. It should be very helpful for newbie and experienced admins alike.

It might be a good idea to have moderators who can do things like roll back the pages to previous versions, or perhaps allow anybody to view previous versions of a page so that anybody can roll back manually. Does your forum software store all revision history for edits, or just the fact that something was edited?

And is there anyway to "sticky" the Index topic?

It would also be really nice if there were a way to view by first letter, instead of having a long list of page numbers. Or, instead of page numbers, have dictionary-style pages, like "aassign-areas" for a page that starts at aassign and goes to areas.

This is a work in progress, your suggestions are most welcome.



It stores an audit trail of all changes. It could be accessed to show a change list, perhaps by piping through diff or something.

However at this stage let's get some changes on board so we can see the "change log" do something useful. Right now you wouldn't see much.



The "index" page is now "stickied" at the top of the topic list. This shows commands in alphabetic order within level. If you happen to know the command name simply use this URL style:

http://www.gammon.com.au/forum/?wiki=look

The list on the topic page (23 pages of it) is sorted into date-modified order, so that is more useful for seeing what recent changes have been made.

I have back-dated the entries a bit so the usual "recent posts" list reappears on the main forum page.

If you make amendments please sign with your name (like Ksilyan and Zeno have done) so we know who to attribute the comments to. Here is an example:

http://www.gammon.com.au/forum/bbshowpost.php?bbsubject_id=6941

Although I wasn't expecting the comments in italics. You can delete the line "Add comments here ..." and just put comments in straight text. :)

Hmm, with the index you have some commands labeled mob commands like mpedit and mpstat. Those shouldn't be there. Also others like mea should be under mpcommands.

As for comments, maybe we could keep them italics to easily tell between documentation and comments?

Oh and is there anyway to tell when the "topic" was created and not just last amended?

Moved them.



Spotted those from the synonyms list, moved them.



Why do you want to know that? They were all automatically created at the same time.



If you want, whatever works best.

I was thinking about that if new topics were created, but I guess they probably won't eh? Whoops. =P

I have edited the index page and grouped the commands into related functions, as best I could. That tends to make the level 0 commands (the bulk of them) more readable by new players to see what they can do.