You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My understanding is that DAB should reduce the frequency of certain MOB brain ticks as the distance from the player increases, but not stop them altogether. (If dab.max-tick-freq is set to the default of 20 for example they should tick at least once per second.) However, I have observed where certain MOBs will freeze indefinitely with DAB enabled, unless the player moves. I have observed this with raiders during raids (pillagers and ravagers), zombified piglins, and wither skeletons. It may happen with other MOB types as well, but I have not been able to confirm this.
I have been able to reproduce this problem with a clean installation of the most recent Pufferfish build (pufferfish-paperclip-1.21.1-R0.1-SNAPSHOT-mojmap.jar), using no plugins and default configuration values. These were the steps I took to set up this installation for testing. I made no config changes:
Create a new directory.
Copy the pufferfish jar to it.
Run the jar to let it create its files.
Edit the eula.txt to accept it.
Run the jar again and stop it.
Copy my world to it.
Run the jar a final time.
In the world I am using for testing I have created a flat circular area approximately 150 blocks in diameter, centered at -403, 95, 171, with a bell, two villagers, and two beds in a fenced in area in the center. If I trigger a raid there by drinking an Ominous Bottle while standing on a platform above the villagers, quite often one or more of the raiders will freeze. When this has happened I have allowed the game to run for more than an hour, and the frozen raider(s) will not move at all during this time, unless I move first.
In the attached screenshot for example, the pillager captain is frozen, while the other pillagers are behaving normally.
If I disable DAB, and make no other configuration changes, the MOBs do not ever freeze.
I have posted about this in #community-support on your Discord, but it seems like an actual bug so I'm also creating this issue here.
My understanding is that DAB should reduce the frequency of certain MOB brain ticks as the distance from the player increases, but not stop them altogether. (If dab.max-tick-freq is set to the default of 20 for example they should tick at least once per second.) However, I have observed where certain MOBs will freeze indefinitely with DAB enabled, unless the player moves. I have observed this with raiders during raids (pillagers and ravagers), zombified piglins, and wither skeletons. It may happen with other MOB types as well, but I have not been able to confirm this.
I have been able to reproduce this problem with a clean installation of the most recent Pufferfish build (pufferfish-paperclip-1.21.1-R0.1-SNAPSHOT-mojmap.jar), using no plugins and default configuration values. These were the steps I took to set up this installation for testing. I made no config changes:
In the world I am using for testing I have created a flat circular area approximately 150 blocks in diameter, centered at -403, 95, 171, with a bell, two villagers, and two beds in a fenced in area in the center. If I trigger a raid there by drinking an Ominous Bottle while standing on a platform above the villagers, quite often one or more of the raiders will freeze. When this has happened I have allowed the game to run for more than an hour, and the frozen raider(s) will not move at all during this time, unless I move first.
In the attached screenshot for example, the pillager captain is frozen, while the other pillagers are behaving normally.
If I disable DAB, and make no other configuration changes, the MOBs do not ever freeze.
I have posted about this in #community-support on your Discord, but it seems like an actual bug so I'm also creating this issue here.
World download: minecraft-dab-test-world.zip
Thanks, and please let me know if I can provide any other info that would be helpful!
The text was updated successfully, but these errors were encountered: