A feedback area designed for scripting and mods suggestions and feedback. Please note bug reports and support issues will be removed.

Please sign in to leave a comment.

  • Official comment
    Nova "inkycatz" Barlow commented

    Please see: 


    "You can use Data Driven Spawning to control which mobs spawn in your worlds"

    We're super excited about these updates and look forward to seeing further discussion on this idea here. 

  • Avatar
    ClayGoddessSari commented

    That would be awesome.  Make the experience more customizeable.

  • Avatar
    WolveReigner781 commented

    BIG YES.  Not that this has been a real problem for me, but adding something like this would really help people on flat worlds who don't want slimes hopping all over the place and their builds.

    doMobSpawning Slime false

  • Avatar
    Robin Rogge commented

    Great idea, I approve!

  • Avatar
    PowerSilver3400 commented

    Yassss im dethly afraid 😱 of endermen 

  • Avatar
    urbeatle commented

    Instead of a gamerule, why not a new tag for datapacks: mobs_spawn_allowed

    Of course, you would also need a mobs subfolder in the tags folder. But that opens the door for a little more flexibility. You could have a mobs_spawn_always tag, which would override the doMobSpawning gamerule (in other words, never turn of spawning for that kind of mob.) Or tags to select which mobs spawn in a given biome (mobs_desert) or on the surface (mobs_surface).

  • Avatar
    Scuidward commented

    this already possible, but only through command blocks. you could make a repeating command block that teleports the entity to the void. for example, in a repeating command block, type /tp @e[type=Creeper] 0 -1000 0.

    P.S. I'm not saying this is a bad idea, just giving a temporary solution. this would require the command block to stay in the spawn chunk at all times, which certainly isn't ideal.

Powered by Zendesk