Bukkit

@shaythegoon No errors in the log?

@johndcastro The first two beta versions (1.7.9 b1/b2, and 1.7.2 b6) tracked the mobs in (spawning) and out (dieing) but this wasn't working because as you say mobs can disappear by other means.

From 1.7.9 b3/1.7.2 b7 I changed that.

Now, every mob that spawns gets added to the database, and when it dies it gets removed. When you use the world-has-spawned condition with no attributes or with only the mob-type attribute that database isn't used and the condition counts the mobs in the world and filters them by type. Then checks the condition using this number and the value you put in the config.

If you have a world-has-spawned condition with mob-id, pack-id, hub-id, or timer-id the database needs to be queried (as Minecraft doesn't store those values usefully). First the same filtering as above is done (if mob-type is used) and then the condition finds all the mobs in the database that are both in the world at the time and match the id attributes.

This does however have a couple of small, unavoidable problems. One is that when you first install the new version the database is empty, so the advanced world-has-spawned condition will only be able to query mobs that have spawned since the plugin was installed. The simple version will still work properly though, and updates to the plugin won't delete all the mobs in the database so this is only when moving to the first version with the DB.

Second is that mobs that get removed without dieing will hang around in the database. They won't have an effect on the world-has-spawned condition though as only mobs currently in the world are counted. I added a spawned_at time column so you can remove all old entries (or in fact any mobs you choose) once in a while. I don't play MC so I'm not sure how long a mob can live but I would think any mobs that are a week old and still in the database are likely safe to remove.

I can confirm that using per-player="yes" will count all the players in the world and then divide the normal value the condition would use by this number. If you like I can add the option to divide by the number of players selected by the timer.

I realize that properties use per-player="x" and conditions use per-player="yes/no" so I will likely be changing one of them so they match in the near future.

Hope that helps :)

@shaythegoon There's already a time condition called world-time, which deals with the ingame ticks.

The other conditions will be coming pretty quickly as I've already written most of them in Mobs :) I'm just deciding which syntax to use for the custom actions and then I can add them.

I have a Windows Phone app in the final stages which I want to push out before switching back to *shudder* Java but it should be done by the end of the weekend.

@shaythegoon This condition is badly formed, which might be causing the whole group to fail to be parsed - <sky-light>1-15</sky-light>

It should be <sky-light>1..15</sky-light>

Also, this will cancel out the inside condition as inside/outside are just convenience aliases for sky-light levels.

@shaythegoon Can you paste your config where you're seeing this happen?

@shaythegoon Mobs can do it, but the next content release of Spawns will include this feature (stolen mostly from Mobs :) )

@shaythegoon Your conditions are stopping the timer before it can start. 0.. means 0 or more, i.e. any number. Try changing it to this:

<start-if>
    <world-has-spawned mob-id="CaveSpiderBoss">0</world-has-spawned>
</start-if>
<end-if>
    <world-has-spawned mob-id="CaveSpiderBoss">1..</world-has-spawned>
</end-if>

@AnorZaken Yes, it is the UUID I'm using as an index. :) I've never even bothered with the other unique id.

Dealing with mobs in Minecraft is a horrible experience as there are so many ways they can disappear. Previous versions of Mobs/Spawns had the list pruned automatically but there were still always problems so this time I've decided to let the admin decide how to handle it. Same with world ids. I'm leaving it up to the admin to manage the database entires when he/she decides to alter the world significantly. I might add a clear command or something to remove all the mobs (or all of x type) though, but this can easily be done with a simple SQL statement that shouldn't be beyond anyone capable of running a server :)

I don't subscribe to to the chunk events any more as they didn't seem to be working as expected and once the mob is in the db it doesn't really matter (other than some space) whether it's in the world or not.

I used to have a world column but it wasn't much use as the count condition grabs all mobs with ids found in the world at the time, so it should never grab any mobs from another world. I included the spawn_location column (with world name) as I might use it in a condition later on (if mob spawned above x=10...)

The next content update will have the feature to perform different actions based on whether the mob is in the db (and what info is there) or if it's vanilla. For example, it will be possible to switch a vanilla pig for a pig from the config when it dies so you can be sure that the loot will match whatever you have in your config, regardless of how it spawned.

Okay, initial testing seems to be holding up so I've released it.

1.7.2 b7/1.7.9 b3 (downloads on the wiki as approval seems to be slow at the moment) now use a database and should fix all the count problems from the last version.

http://wiki.sylian.eu/spawns/world-has-spawned had to change slightly so the page is updated.

http://wiki.sylian.eu/spawns/tracked-mobs now describes the database.

Last big change is that end-if is now checked before any mob spawns (previously it was only checked after each mob). This means you can do this

<timer>
    <end-if>
        <world-has-spawned>100..</world-has-spawned>
    </end-if>
</timer>

instead of having specific start and end conditions.