btmux-0.6-rc4/doc/
btmux-0.6-rc4/event/
btmux-0.6-rc4/game/
btmux-0.6-rc4/game/maps/
btmux-0.6-rc4/game/mechs/
btmux-0.6-rc4/game/text/help/
btmux-0.6-rc4/game/text/help/cat_faction/
btmux-0.6-rc4/game/text/help/cat_inform/
btmux-0.6-rc4/game/text/help/cat_misc/
btmux-0.6-rc4/game/text/help/cat_mux/
btmux-0.6-rc4/game/text/help/cat_mux/cat_commands/
btmux-0.6-rc4/game/text/help/cat_mux/cat_functions/
btmux-0.6-rc4/game/text/help/cat_templates/
btmux-0.6-rc4/game/text/wizhelp/
btmux-0.6-rc4/include/
btmux-0.6-rc4/misc/
btmux-0.6-rc4/python/
btmux-0.6-rc4/src/hcode/btech/
btmux-0.6-rc4/tree/
& @wait
 
  Syntax: @wait <seconds>=<command>
           @wait <object>[/<seconds>]=<command>
           @wait <object>/<attribute>=<command>
 
  The first form of @wait executes <command> after <seconds> seconds. 
  The second form increments the semaphore count for <object> and 
  executes <command> after <object> is notified with the @notify 
  command.  If the semaphore count for <object> is negative (because 
  it has been notified more times than it has been waited on), then 
  <command> is run immediately.
  
  If <seconds> is specified in the second form, the command is
  automatically run after <seconds> seconds even if the semaphore 
  isn't notified. 
  
  The third form allows for blocking multiple sets of commands on 
  the same object, using seperate attributes to keep track of the 
  semaphore.

  This command charges a deposit of 10 coins, which is refunded when
  <command> is executed.
 
  See also: @drain, @notify, @ps, SEMAPHORES