[Crossfire-wiki] [Crossfire DokuWiki] page changed: dev:objects

no-reply_wiki at metalforge.org no-reply_wiki at metalforge.org
Fri Dec 8 05:54:57 CST 2006


A page in your DokuWiki was added or changed. Here are the details:

Date        : 2006/12/08 05:54
User        : ryo
Edit Summary: format

@@ -1306,33 +1306,23 @@
  push the connected objects.  By default, pedestals match players.  They
  differ from buttons in that specific objects activate them (vs an amount of
  weight.)  They are different from altars in that the object that
  activates them does not disappear.
+ 
  
  ==== Inventory checkers (64) ====
  
- Inventory checkers passively check the players inventory to see if it
- contains some object.  Thus, you can make portals which you can't pass through
- if you contain certain objects.
+ Inventory checkers passively check the players inventory to see if it contains some object.  Thus, you can make portals which you can't pass through if you contain certain objects.
  
- slaying:  Object name we are looking for.
- race: archetype name we are trying to match for.
- hp: match on object with that type value.
- last_heal: Remove object if found.
- last_sp: If set, than having that object is a match.  If 0, then not having
-   that object is a match.
- connected:  Value to to push.
- no_pass: If set, you can only pass through that space if you be allowed to
-   (depending on last_sp determines if having/not having is the match
-   criteria.)  if no_pass is 0 (default), then the inventory only acts as
-   a trigger/button.
+ | slaying | object name we are looking for |
+ | race | archetype name we are trying to match for |
+ | hp | match on object with that type value |
+ | last_heal | remove object if found |
+ | last_sp | if set, than having that object is a match.  If 0, then not having that object is a match |
+ | connected | value to to push |
+ | no_pass | if set, you can only pass through that space if you be allowed to (depending on last_sp determines if having/not having is the match criteria). If no_pass is 0 (default), then the inventory only acts as a trigger/button |
  
- General usage notes:  Putting a check_inventory space in front of a gate with
- another on the other side works reasonably well as a control mechanism.  Note,
- however, that other people may still be able to slip by.  To get around this,
- use the no_pass to 1, and put it in the space you want to control (probably
- makes sense to put a fake door or other object there to make it a little more
- obvious what is going on.)
+ General usage notes:  Putting a check_inventory space in front of a gate with another on the other side works reasonably well as a control mechanism.  Note, however, that other people may still be able to slip by.  To get around this, use the no_pass to 1, and put it in the space you want to control (probably makes sense to put a fake door or other object there to make it a little more obvious what is going on.)
  
  ==== Detector ====
  
  This object samples the square its in, and if it finds an object


IP-Address  : 213.174.127.3
Old Revision: http://wiki.metalforge.net/doku.php/dev:objects?rev=1165578762
New Revision: http://wiki.metalforge.net/doku.php/dev:objects

-- 
This mail was generated by DokuWiki at
http://wiki.metalforge.net/




More information about the crossfire-wiki mailing list