[Bug Report] Ghasts Butchering

Discussion in 'Help & Support / Errors & Bugs' started by Fon_, Jul 22, 2019.

  1. Fon_

    Fon_ Kindhearted Shade
    Resident ⛰️ Ex-EcoLeader ⚜️⚜️⚜️ Premium Upgrade

    Joined:
    May 26, 2014
    Messages:
    818
    Trophy Points:
    54,910
    Gender:
    Male
    Ratings:
    +411
    Minecraft Username:
    Fon_

    Brief Description:
    Ghasts don't get consistently butchered


    Instructions:

    I have a 3 ghast spawner setup and they get randomly butchered, having hours of not being butchered allowing them to stack in huge numbers. Sometimes is 400 ghats other times over 2k.

    How many times did you recreate this?
    5+

    Result:
    Huge amount of ghasts stacking

    Expected Result:
    Being butchered at the same rate as other mobs.
     
    • Informative Informative x 1
    • List
  2. andrewkm

    Founder Premium Upgrade

    Joined:
    Apr 5, 2011
    Messages:
    20,679
    Trophy Points:
    102,160
    Ratings:
    +15,143
    Not a bug.
    You’re suggesting a feature, which won’t be implemented.
     
  3. Budkiss

    Budkiss Builder
    Builder ⛰️ Ex-Tycoon ⚜️⚜️⚜️

    Joined:
    May 20, 2019
    Messages:
    67
    Trophy Points:
    23,770
    Gender:
    Male
    Ratings:
    +35
    I dont think you are understanding andrew. So the ghasts currently arent getting butchered like the rest of the mobs causing them to stack up to 4500 ghasts at a time. When they should only maybe be getting to a couple hundred maybe then get butchered at the 10 minute mark. When thats not the case and they are not disappearing at the 10 minute mark.
     
  4. andrewkm

    Founder Premium Upgrade

    Joined:
    Apr 5, 2011
    Messages:
    20,679
    Trophy Points:
    102,160
    Ratings:
    +15,143
    Ah makes sense.
    I have confirmed this bug and it is now in our development to-do list.
     
  5. andrewkm

    Founder Premium Upgrade

    Joined:
    Apr 5, 2011
    Messages:
    20,679
    Trophy Points:
    102,160
    Ratings:
    +15,143
    This should now be fixed.