The Aether

The Aether

Mods
53M Downloads

Bug: Can't craft with holystone mined with silk touch

ImTestingWisdom opened this issue ยท 1 comments

commented

What Feature Types Apply to This Bug?

Block

Other Type

No response

What Type of Bug Is This?

Unexpected Behavior

Mod Loader

Forge

Mod Loader Version

14.23.5.2860

The Aether Version

aether-1.12.2-v1.5.4.1

Is This Bug a Conflict With Another Mod?

No response

Client Log

https://gist.github.com/ImTestingWisdom/c2631650bdfc4ff1310d92e6c4567b5b

Crash Report (if applicable)

No response

Steps to Reproduce

Always happens

  1. Mine holystone without silk touch
  2. Craft anything with holystone, works4. Mine holystone with silk touch
  3. Craft anything with holystone, doesn't work
  4. Put both mined blocks in one stack
  5. Can't craft

What You Expect To Happen

The mined blocks either get separated or you can craft with silk touch mined holystone

What Actually Happened

You can put silk touch mined holystone and normal holystone in one stack and you can't craft anything with silk touch holystone

Additional Details

https://www.youtube.com/watch?v=rbOyrkfW66g

Image

Image

You can trick the crafting recipe if you first mine without silk touch and then with silk touch, this allows the silk touch holystone to be used for crafting

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 contain vague information (ie. Versions are properly recorded, answers to questions are clear).
  • I have confirmed this bug is unique and has not been reported already.
  • If playing on a modpack, I have reported this bug to their issue tracker already.
  • I have confirmed that I'm reporting a bug in The Aether I, not The Aether II.
commented

The 1.12.2 version is no longer really supported; I'm not sure what'd cause this weird issue other than probably something different with how blockstates worked in the past.