Bukkit

@Xikage Found and fixed the area one, looking into the second one now.

@Xikage Types of element are now divided into subgroups, rather than all being together. So it should look like this:

<spawn_mob>
  <amount>20</amount>
  <mob>zombie</mob>
  <world>Ixtalia</world>
  <target>
    <area>test</area>
    <around>
      <mob>pig</mob>
      <amount>3</amount>
      <x>5:3</x>
      <y>0:0</y>
      <z>10:8</z>
   </around>
  </target>
</spawn_mob>

In XML the indentation is optional, so you can lay it out however you want, as long as the parent-child relationship is right.

@Xikage Not yet, but relatively soon.

I'll see if I can find a way to differentiate between real players and NPCs.

@Xikage The syntax changed a little and looks like this now:

<repeating_outcomes>
  <outcome interval="5">
    <conditions>
      <not_raining>
        <world>Ixtalia</world>
      </not_raining>
    </conditions>
    <actions>
      <spawn_mob>
        <amount>1</amount>
        <mob>zombie</mob>
        <world>Ixtalia</world>
        <target>
          <around>
            <mob>player</mob>
          </around>
         </target>
      </spawn_mob>
    </actions>
  </outcome>
</repeating_outcomes>

I updated most of the pages on this site last night and today I'm doing the example file.

Beta 9 is up - linky

• Fixes a bug with worlds set in conditions and actions
• world can now be set inside the condition/action or inside the target element

<spawn_mob>
  <world>world</world>
  <mob>pig</mob>
  <target>
    ...
  </target>
</spawn_mob>

<spawn_mob>
  <mob>pig</mob>
  <target>
    <world>world</world>
    ...
  </target>
</spawn_mob>

are the same now. The one inside target will be ignored if they are both present.

• fixed a bug with string conditions (spawn_reason, etc.)

@nhoclesnar It's refreshing to work with Silverlight after too much Java :)

More stuff:

• action elements now can only be set once. Different versions must be children of the elements.

<action_name>
  <mob>
    <value>1</value>
    <value>2</value>
  </mob>
  <target>
    ...
  </target>
  ...
</action_name>

Simple values don't need to be children but can be put directly into the element

<action_name>
  <message>text</message>
</action_name>

Really simple values can go straight into the action name itself

  <log>text</log>

• Specifying the world for conditions or actions (if necessary is now done inside the target element. Unlike all other targets, world is always applied and not chosen by ratio (although it's possible to specify multiple worlds and have one chosen by ratio).

• Properties can now be set on other mobs than the event mob by using a target element.

After lots of work (3700+ lines of code changed!) Beta8 is up.

Although it's called Beta this might be a slight regression for some configs. The simple fact is with that many changes I'm finding it a little hard to see the wood for the trees. So it's important to let me know what isn't working as expected.

The main changes are to the config syntax, although there are a few normal changes as well.

Normal changes

• Added chunk_mob_count condition

This will tell you the amount of mobs in the same chunk as the target. Every mob is supported, as well as all mobs and all mobs with a certain name (of a certain type). The syntax looks like this:

<chunk_mob_count>
  <mob>pig:test</mob>
  <amount>above 3</amount>
</chunk_mob_count>

This example will count the number of pigs with the name test. The mob element is optional. Without it all mobs will be counted. To count all pigs leave the :test off.

Conditions can also have targets now (without the target element they use the mob in the event). See below for more explanation.

<chunk_mob_count>
  <target>
    <player>coldandtired</player>
  </target>
  <mob>pig:test</mob>
  <amount>above 3</amount>
</chunk_mob_count>

Now it counts how many pigs called test are in my chunk, no matter where the original mob is.

• Added Metrics back. You can opt-out by changing Metrics' config if you really want to.

• Added a new log_level 2, which warns you when actions don't perform due to missing stuff. Not very useful yet.

• Added new actions clear_data, set_hp, set_max_hp, set_money

clear_data removes all of the custom data (that the plugin stores) from a mob. Most useful for players as the data stays there when they die.

set_hp and set_max_hp are now implemented. Note that setting one of them will only set the other if it needs to. E.g. setting max_hp to 40 will not change the hp unless the old hp was higher than 40, in which case it will reduce it to 40.

set_money needs Vault and an economy plugin installed.

Both the hp and money actions use the new number format, which looks like this: <<code XML>> <set_money> <amount>40:+%</amount> </set_money> <</code> The second part of the number is optional. Use + to add the amount to the current value, - to subtract it, and % to make it a percent value. Without these it will be absolute.

• near is now called around.

• The settings element now has an optional attribute called ignored_worlds which will cause the plugin to skip any events happening in those worlds. Separate each world with a comma.

• more coming!

You can download it here

@dexyh1234 Sounds easy enough :)

Marsolic is right.

I find ratios to be cleaner and easier than percentages.

For the admin

• you don't have to worry about making the total 100%
• you don't run into problems with things like 66.6666666666666667%
• you don't have to remember whether you need to include the % sign or not
• adding or removing a value is easy (as far as I can remember, it's possible to set a ratio to 0 to temporarily disable it without messing with the other values.
• as Marsolic wrote, it's possible to make it into percentages by specifically setting the ratios to add up to 100 (all ratios must be set as a value without a ratio is set to 1)

For me

• I don't have to decide what to do if the admin makes a mistake with the total (show an error? use previous percentage?, etc.)
• I don't have to constantly adjust the amount of decimal places to check for