Gammon Forum

(You can't go that way!|You inhale a lot of water and pause to catch your breath.|What ?|You aren't skilled enough to go there!)

Valid commands>
  A) Accepts 4e, etc. But most muds use 4 e, so typing that
  will mess it up, since it doesn't know how many directions
  where actually added. Fixing is simple.
  B) You can't set things like 'climb *', 'fly *', etc. as
  valid options, you have to insert them manually, which
  isn't very automatic.

Invalid exit deletion>
  Currently mushclient doesn't bother to check if an invalid
  response is produced 'only' after a valid movement. So any
  command that triggers an invalid messages erases the last
  one in the list of stored moves. (It would help if all muds
  had a seperate message for movement and for commands,
  but...) This is however not hard to fix, as long as the
  mapper knows what are valid direction commands and only
  responds with a deletion if the fail message follows an
  actual direction command. The only other option is to
  capture 'all' commands in the mapper and that would be
  counter productive.

Exits & Room name>
  Room name is 'partially' fixed, but only for muds that
  use MXP or happen to work with the capture plugin Nick
  designed. Some may not be fixable, but most have some
  color, etc. that could maybe capture the title (again
  you need to make sure that this is only done after
  some valid movement, or other things could get captured
  if you want it to always work right.) Providing a direct
  non-script way to set up the needed matching for this
  could be nice, since I am not sure how you could do it
  otherwise.

  A trigger assumes that 'any' line that is color x will be
  a room name and that is not a valid assumption, nor is
  there any way to use the mapper to tell such a script
  that it should be looking. To do so, the mapper would
  have to, again, keep track of valid moves and have a
  'call this script on a valid move' setting. Then you
  could use that script to turn on the needed triggers and
  the triggers themselves to do the capture and turn
  themselves back off.

if World.GetLinesInBufferCount() != varLastLineNum :
     varThisLineNum = World.GetLinesInBufferCount()
     for x in range(varLastLineNum, varThisLineNum) :
          ScriptParseDef(World.GetLineInfo(x, 1)) 
          #1 is line text
     varLastLineNum = varThisLineNum