[Solved] How do I fix my random spawning issues. No custom mobs will random spawn.

Discussion in 'Community Support' started by pinkpig3777, Jun 25, 2017.

  1. pinkpig3777

    pinkpig3777 Member

    Joined:
    Jun 23, 2016
    Messages:
    212
    Likes Received:
    14
    [Solved]

    I noticed a while ago that I wasn't finding custom mobs in the world but didn't really think much of it at the time. It's been quite a while now and I still haven't seen ANY custom mobs spawn randomly throughout the world. Clearly, something is wrong but I'm not sure what I changed that made it this way. Please help me fix this issue.

    Server version: Spigot 1.10.2
    Plugins: http://prntscr.com/fnz0lv

    My MythicMobs Folder Download: http://preview.tinyurl.com/yctf3ys7
    MythicMobs reload message: http://prntscr.com/fnz060
    MythicMobs plugin version: MythicMobs-4.1.0-SNAPSHOT

    Thank you!
     
    #1
    Last edited: Jul 14, 2017
  2. BerndiVader

    BerndiVader Active Member
    Supporter

    Joined:
    Feb 9, 2016
    Messages:
    602
    Likes Received:
    220
    Hello! You need to update a few things in your yamls.

    Most of your randomspawners use
    Code:
    Action: ADD
    And that this work you need to set
    Code:
    GenerateSpawnPoints: true 
    in your config.yml. Atm you have it at false. Beside of that, its an outdated config.yml. I suggest you delete it and let mm create a 4.0 config. Then adjust the spawner settings again.

    And then there are some faults in the conditions anyway. Like this one:
    Code:
    RandomWitchOfTheWaste:
      Action: ADD
      Worlds: world
      MobType: Witch
      Chance: 0.01
      Priority: 3
      UseWorldScaling: true
      Conditions:
      - worldtime 13801-22200
      - mobtype WITCH
    This will not work very well. If you use ADD there is never a bukkit entity to compare with. If you want to replace the bukkit witches use Action: REPLACE.

    There is another thing:
    Code:
      Conditions:
      - outside true
      - onblock grass
      - biome SAVANNA
      - biome SAVANNA_PLATEAU
      - biome ROOFED_FOREST
    If you want that the mob with this condition spawn in SAVANNA, SAVANNA_PLATEAU and ROOFED_FOREST you cant use it this way. Lets say the location is in SAVANNA_PLATEAU, the mob will never spawn there because the first biome condition say SAVANNA and is false, it will not check the other conditions and cancel the spawn. Use just one biome condition for this:
    Code:
    - biome{b=SAVANNA,SAVANNA_PLATEAU,ROOFED_FOREST}
    Maybe there are other issues too, havent looked further.
     
    #2
  3. pinkpig3777

    pinkpig3777 Member

    Joined:
    Jun 23, 2016
    Messages:
    212
    Likes Received:
    14
    Okay thank you!
    Also for:
    Code:
    RandomWitchOfTheWaste:
      Action: ADD
      Worlds: world
      MobType: Witch
      Chance: 0.01
      Priority: 3
      UseWorldScaling: true
      Conditions:
      - worldtime 13801-22200
      - mobtype WITCH
    Should MobType always be the vanilla mob? Or the MythicMobs mob name? For example, with the SkeletonKing should I be putting "MobType: SkeletonKing" or "MobType: Skeleton"?

    Also I changed everything you mentioned and changed a lot of the mobs to "REPLACE" instead of "ADD" except most bosses. And now a TON of bosses are spawning at once.. Lol.. How do I fix that? Just switch them all back to add? :p
     
    #3
    Last edited: Jun 25, 2017
  4. BerndiVader

    BerndiVader Active Member
    Supporter

    Joined:
    Feb 9, 2016
    Messages:
    602
    Likes Received:
    220
    :) K Usually the tons of mobs are spawning with add.

    In my opinion (yes i know its mentioned in the manual that it is for randowmspawners), the condition mobtype (compares for mythicmobs types) is useless in randomspawns because 1. it can only be used in replace and there is never a MythicMob spawned by bukkit, use entitytype instead.

    Anyway, your randomspawners need some fine tuning. Keep in mind that if you use conditions that compare to entity behaviours there is an entity needed, and that entity is not the mob that will be spawned, its the entity that will be replaced and therefor it doesnt work for ADD because there is no entitiy, it only works for REPLACE.
     
    #4
    pinkpig3777 likes this.
  5. pinkpig3777

    pinkpig3777 Member

    Joined:
    Jun 23, 2016
    Messages:
    212
    Likes Received:
    14
    I don't use randomspawners yet though. Just random spawns. Unless that was a typo.

    Edit: Oh wait by RandomSpawners you mean the randomly generated points right? Not actual mob spawners.
     
    #5
    Last edited: Jun 25, 2017
  6. pinkpig3777

    pinkpig3777 Member

    Joined:
    Jun 23, 2016
    Messages:
    212
    Likes Received:
    14
    Well I'm incredibly confused. When I change them all to "ADD" tons of mobs spawn. Then when I change them all to "REPLACE" no mobs spawn. At this point, I'd pay someone $15 to go through my latest MythicMobs folder and balance it so they spawn in regular amounts except for bosses which should be more rare. :p
    (Seriously though, I'd pay)

    The main thing that confuses me is I'm using the same priority levels, action, and chance of spawning that I used to use when MythicMobs worked fine and had balanced spawning, yet it still doesn't work.

    Latest Folder:
    http://preview.tinyurl.com/y9fwazoj
     
    #6
    Last edited: Jun 25, 2017
  7. pinkpig3777

    pinkpig3777 Member

    Joined:
    Jun 23, 2016
    Messages:
    212
    Likes Received:
    14
    Still trying to figure out what I'm doing wrong while trying to balance the mob spawning for MythicMobs. My previous message explains my issue.
     
    #7
  8. pinkpig3777

    pinkpig3777 Member

    Joined:
    Jun 23, 2016
    Messages:
    212
    Likes Received:
    14
    Sorry for very late reply, I've been very busy in real life.

    (1) So when it is entitytype do I name a vanilla mob type? or a mythicmobs mob name?

    (2) Also what you're saying is, for ADD conditions will not work? and that conditions will only work for REPLACE?
     
    #8
    dat1noob likes this.
  9. BerndiVader

    BerndiVader Active Member
    Supporter

    Joined:
    Feb 9, 2016
    Messages:
    602
    Likes Received:
    220
    @pinkpig3777 : What i try to say is that there are conditions that only work if a entity is present to compare with. Entitytype is such a condition. If used in randomspawn it check if the bukkit entity that should be REPLACED match. (Yes its about vanilla entitytypes. https://hub.spigotmc.org/javadocs/spigot/org/bukkit/entity/EntityType.html) The biome condition should be an location condition. But its a condition for entities & locations. Thats fine aslong as its used in skills. But because of an issue in MythicMobs you cant use that condition in randomspawn because if used there MythicMobs always try to compare with entity. Thats ok for REPLACE but for ADD where only a location is present it throws an error.
     
    #9
    pinkpig3777 likes this.
  10. pinkpig3777

    pinkpig3777 Member

    Joined:
    Jun 23, 2016
    Messages:
    212
    Likes Received:
    14
    Sorry for late reply.

    I think I finally balanced it! Thanks! :D
     
    #10

Share This Page