Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Placing down backtanks will remove Quark's Runic Etching #6225

Closed
Frosticle opened this issue Mar 8, 2024 · 1 comment · Fixed by #6662
Closed

Placing down backtanks will remove Quark's Runic Etching #6225

Frosticle opened this issue Mar 8, 2024 · 1 comment · Fixed by #6662
Labels
area: compatibility Issue only happens when other mods are present type: bug Issue where something isn't working

Comments

@Frosticle
Copy link

Describe the Bug

When you change the backtank's enchantment glint with the Quark mod's Runic Etching smithing template, then place the backtank down as a block, and pick it up again, the runic etching is removed. This happens to both copper and netherite backtanks.

Reproduction Steps

  1. Enchant the backtank.
  2. Apply a runic etching to the backtank in the smithing table.
  3. Place the backtank down as a block.
  4. Pick the backtank back up.

Expected Result

The backtank retains it's runic etching.

Screenshots and Videos

2024-03-08.09-02-50.mp4

Crash Report or Log

No response

Operating System

Windows 11

Mod Version

0.5.1f

Minecraft Version

1.20.1

Forge Version

47.2.18

Other Mods

No response

Additional Context

No response

@Frosticle Frosticle added the type: bug Issue where something isn't working label Mar 8, 2024
@VoidLeech
Copy link
Collaborator

Same underlying issue as #6186.

@IThundxr IThundxr added the area: compatibility Issue only happens when other mods are present label Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: compatibility Issue only happens when other mods are present type: bug Issue where something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants