Alaska Native Craft

Alaska Native Craft

567k Downloads

[BUG] Seals pick a direction and travel in it indefinitely

riverbanksquid opened this issue ยท 2 comments

commented

Describe the bug
When seals are spawned from spawn eggs, they immediately start traveling in whatever direction they're facing. They'll run into an obstacle and just kind of push against it until they get past, or get stuck there. They perform no other behaviors (except making sounds and looking at the player). I tried spawning about 40 in a row and 39 of them took off (one stuck around, even when I shoved it a little).
I have not seen a seal spawn naturally yet, so I can't say whether naturally-spawning ones also do this.
Neither moose nor ptarmigan seem to have this issue.

To Reproduce
Steps to reproduce the behavior:

  1. Use a seal spawn egg in any game mode
  2. Watch it go

Mod Versions (please complete the following information):

  • Minecraft Version: 1.17.1
  • Fabric API Version: 0.41.0+1.17 [Loader 0.11.7]
  • Conflicting Mod (if any)'s Version: N/A
  • This Mod's Version: 1.3.1

Additional context
Out of everything I have installed, I thought possibly Krypton was the most likely one to have caused this, but I removed it and the bug persisted. Couldn't begin to guess what else it could be.
The following 2 lines are the only ones in the log that seem remotely related (maybe) (no idea what those classes are).

[12:05:53] [main/WARN]: @mixin target net/minecraft/class_3218$class_5526 is public in fabric-lifecycle-events-v1.mixins.json:ServerWorldEntityLoaderMixin and should be specified in value
[12:05:53] [main/WARN]: @mixin target net/minecraft/class_3898$class_3208 is public in fabric-networking-api-v1.mixins.json:accessor.EntityTrackerAccessor and should be specified in value

commented

Sorry that it took so long to respond, I found the cause. Seals faced the opposite direction of their target position, so when they traveled forwards, they traveled in the wrong direction, therefore infinitely trying to get to an unobtainable point. This is finally fixed in 1.3.3, which should be released very very shortly

commented

I've been thinking I should get back around to testing this without a bunch of other mods installed since this was kind of a sloppy bug report (my bad..) & you went ahead and figured it out anyway...! I'm SO stoked; thank you for your hard work!!