The Aether

The Aether

32M Downloads

Bug: Swets have odd behavior on Slime Blocks

Zepalesque opened this issue ยท 7 comments

commented

What Feature Types Apply to This Bug?

Block, Entity

Other Type

No response

What Type of Bug Is This?

Unexpected Behavior

Forge Version

45.1.0

The Aether Version

beta.5.1

Is This Bug a Conflict With Another Mod?

No response

Client Log

No response

Crash Report (if applicable)

No response

Steps to Reproduce

Step 1: Place a Slime Block
Step 2: Spawn a Swet on that Slime Block
Step 3: Observe

What You Expect To Happen

The Swet would be able to properly navigate on the Slime Block

What Actually Happened

The Swet got stuck on the block, seemingly trying to infinitely jump

Additional Details

Video of the bug:

Minecraft_.1.19.4.-.Singleplayer.2023-08-02.17-00-19.mp4

Please Read and Confirm The Following

  • I have confirmed this bug can be replicated without the use of Optifine.
  • I have confirmed this bug is on the most recently supported version of Minecraft.
  • I have confirmed the details provided in this report are concise as possible and does not contained vague information (ie. Versions are properly recorded, answers to questions are clear).
  • I have confirmed this issue is unique and has not been reported already.
  • If playing on a modpack, I have reported this issue to their issue tracker already.
commented

Can you get a video of this without any other mods.

commented

Could you get a video of it affecting vanilla slimes too?

commented

alright, here (sorry about the short video length, my recording software refused to make it under 10 MB otherwise lol):

Minecraft_.1.19.4.-.Singleplayer.2023-08-02.17-10-28.mp4

another thing I found out right after making the issue report is that this also affects vanilla slimes, not sure if that affects whether or not it will get fixed but I thought I'd note that either way

commented
slimes.mp4
commented

While this is a vanilla bug, I think I'll still look into the animation speed of the Swet during this.

commented

Okay apparently this is something I already fixed in my cleanup branch

commented

Reopening so it can be closed by the merge of the branch.