Denizen/0.7/Interact Scripts/Interact Requirements: Difference between revisions

From Citizens Wiki
m (→‎Script: Fixed SCRIPT syntax.)
m (→‎World: Added ISLIQUID requirement.)
Line 67: Line 67:
<div style="margin-right:2.0em; padding:10px; font-family:museo-sans; font-size:110%;">
<div style="margin-right:2.0em; padding:10px; font-family:museo-sans; font-size:110%;">
{{Denizen Requirement Type Color|aliceblue|
{{Denizen Requirement Type Color|aliceblue|
[[Interact_Script_Requirements#Powered|POWERED]]
[[Interact_Script_Requirements#Isliquid|ISLIQUID]]
| &nbsp;&nbsp;<nowiki>[Block Bookmark]</nowiki>
}}
 
<div style="margin-right:2.0em; padding:10px; font-family:museo-sans; font-size:110%;">
{{Denizen Requirement Type Color|aliceblue|
[[Interact_Script_Requirements#Ispowered|ISPOWERED]]
| &nbsp;&nbsp;<nowiki>[Block Bookmark]</nowiki>
| &nbsp;&nbsp;<nowiki>[Block Bookmark]</nowiki>
}}
}}

Revision as of 14:09, 9 October 2012

Requirements

Requirements set criteria for your scripts to check against. They provide a powerful way to have a variety of interaction possibilities with Denizen NPCs. Imagine NPCs that will offer you some fish when hungry, or a shopkeeper that can sell you goods. These are two of many things made possible with the use of Requirements.

Note: Requirements from 0.6 are in-tact for 0.7, but will now be referred to as 'Legacy Requirements'. They will be slowly replaced with new commands that will override functionality. The new systems allows for improved tolerence better debugging, as well as make it easy for other plugin programmers to extend Denizen. Just a heads up. This page will keep you informed of any changes.

[] indicates required field, () indicates an optional field, | indicates alternative usage.

Click on any requirement to get more information and example usages.

Player

  [> or < or =] [# or %]
  [ITEM_NAME or #:#] (Quantity)
  [Full or Hungry or Starving]
  [ITEM_NAME or #:#] (Quantity)
  [# or higher]  OR  LEVEL  [At least this Level #]  [No more than this Level #]
  [Player Name]  (Player Name)  (Player Name) ...
  
  [POTION_TYPE]
  
  [ITEM_NAME or #:#]

World

  [Block Bookmark]
  [Block Bookmark]
  
  
  [Day or Night or Dusk or Dawn or TIME 0-23999]
  [World Name]  (World Name)  (World Name) ...

Script

  [Name of Activity]
  (# of times)  [Script Name]
  (# of times)  [Script Name]
   [FlagName:FlagValue or FlagName] (EXACTLY) (PLAYER or DENIZEN or GLOBAL)
   [FINISHED or FAILED or STEP] (STEP:#) (QTY:#) (EXACTLY) [SCRIPT:scriptname]

Permission/Economy

These requirements only work if you have Vault installed and a compatible permissions/economy plugin.

  [Group Name]  (Group Name)  (Group Name) ...
  [Quantity]
  [permission.node]

Negative Requirements

Requirements can also be 'negative' requirements. In the Requirements List, just place a '-' in front of the requirement to inverse its logic. For example, 'HOLDING IRON_SWORD' would require the player to be holding an Iron Sword. '-HOLDING IRON_SWORD' would require the player to NOT be holding an Iron Sword. All requirements have a negative alternative, even ones whose function may overlap, such as '-WEATHER Precipitating' and 'WEATHER Sunny', which technically do the same thing. If anything, it can add to script readability. The negative requirement '-' should not be confused with the 'list item -' with a trailing space in front of each Requirement in the List, as that is standard YAML list format. See below:

 Requirements:
   Mode: All
   List:
   - -TIME Night
   - -MONEY 1000000
   - -STORMY

Negative requirements can completely change the original example around. In this 'revised' example, for this script to trigger, time needs to be day, the weather in the current world must NOT be storming, and the player have less than 1000000 units of currency on them.