Bukkit

@colin8696909 This is all you need to do

zombie:
  spawn_rules:
    spawn: no

It's very important in YAML to get the indentation right (unfortunately).

@tappestry This plugin (Mobs) is maybe too passive towards other plugins. What I can do is turn up the priority on the events to be more aggressive and overrule what other plugins have done.

It makes sense seeing as how all of the conditions in the plugin are controlled by the admin. Something for the next version.

1.9 b3 is up - direct link

Changes

• Replaced the /sm command. There is one difference from the last version (pre 1.9) and that is that /sm name will activate all the shortcuts called name. This way you can group mobs together if you want to do things manually.
• Added a global config setting - auto_spawn_min_player_count. Set this to a number to deactivate the auto-spawning if few than x players are on the server.
• Changed the auto_spawn block slightly. It now looks like this

  auto_spawn:
  - spawn_event:
      where_to_spawn:
      - location:
          players: [coldandtired]
          range: {x: 1, y: 1, z: 1}
      - location:
          players: [all_players]
      - location:
          worlds: [world1, world2, world3]
  

• world is now called worlds, and takes a list of names. The auto_spawns will be set up on each world in the list.
• Now, using only worlds without a region, range, or base will use all the loaded chunks as the possible spawn positions. Loaded chunks are close to players so test this carefully.
• A new key called players is now possible. This takes a list of player names or the text all_players. The plugin will loop though the players in the list (or all players) and spawn the mob(s) within 5 blocks of the player. This 5 blocks can be overridden by adding a range key as in the example above.
• Fixed the create_portal mistake as seen below.

@KubaBVB09 You have to post your whole config file.

@tappestry If the config is empty then the plugin isn't doing anything. It only reacts to mobs set up in the config.

I had a look at the Catacombs code and it blocks spawners when the light level is above 10. Is this what you're seeing?

@KubaBVB09 Post your whole config.yml either here or to Pastebin. Are you using 1.9 b2?

@LanToaster It should do, but upon checking the code I've just seen that I made a stupid mistake and reversed the result :(

So create_portal: no will do the opposite of what it should. I'll fix it tonight but you can set it to yes if you want to play with it now.

@LanToaster /rm is temporarily disabled while I was making sure the rest of the plugin worked okay.

Your config looks fine. I think the problem is simply numbers. Your potential auto_spawn area is 20000 x 20000 x 116, which is 46,400,000,000 blocks. You also only want the blazes to spawn in the desert and hell biomes. Obviously a fair few of these blocks are dirt and stone and whatever, but it still leaves quite a small chance of seeing one of those blazes spawn near a player.

I recommend you try testing the config before expanding it - set the quantity to 1, the base and range to a small area where you can observe it, and the spawn_interval to something like 60 (to give you time to change the config - change the quantity to 0, for example, and reload the plugin before you get flooded by mobs).

The auto_spawn mobs are created independently of anything Bukkit or another plugin is doing. Any mobs created with spawn_rate will be in reaction to other mobs spawning (from whatever source).

@tappestry Can you tell me more about the conflicts (or privately if you prefer)? Are error messages being generated? What is happening that isn't supposed to or vice versa?

@KubaBVB09 It works fine for me. Your config.yml (the other files don't do anything now) should have this section in it

blaze:
  death_rules:
  - action:
      replace_drops: yes
      will_drop:      
      - item:
          names: [nothing]