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

MC|ItemName is an unknown channel. (Related to Anvils) #354

Open
FastFelix771 opened this issue Aug 23, 2016 · 2 comments
Open

MC|ItemName is an unknown channel. (Related to Anvils) #354

FastFelix771 opened this issue Aug 23, 2016 · 2 comments

Comments

@FastFelix771
Copy link

FastFelix771 commented Aug 23, 2016

When i click with an item into a Anvil, the following message appears in the console: (removed log level etc.)
FastFelix771 used unknown Minecraft channel: MC|ItemName

The minecraft client probably sends some packet(s) that acts with anvils?

EDIT:
This happens on EVERY action in the anvil.
Even if i wanna change the item name, on every letter i enter, the message appears.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@FastFelix771
Copy link
Author

FastFelix771 commented Aug 23, 2016

If i repair a enchanted diamond pickaxe, this thing appears in the console:
[rejected] WindowClickMessage(id=11, slot=2, button=0, transaction=21, mode=0, item=ItemStack{DIAMOND_PICKAXE x 1, UNSPECIFIC_META:{meta-type=UNSPECIFIC, enchants={DURABILITY=3, LOOT_BONUS_BLOCKS=2, DIG_SPEED=4}}})

Also, i get the repaired item, and the broken one.
Items duplicate.

And randomly, it also deletes, the broken pick, the new one and all 64 diamonds from my inventory.

@aramperes
Copy link
Member

Partially fixed in 2aad4f0

@gdude2002 gdude2002 added this to Backlog in March 2017 Feb 27, 2017
@gdude2002 gdude2002 moved this from Backlog to Stalled in March 2017 Feb 27, 2017
@mastercoms mastercoms added this to the 2017.3 milestone Mar 4, 2017
@mastercoms mastercoms moved this from Stalled (Little activity since '16) to In Progress in March 2017 Mar 9, 2017
@gdude2002 gdude2002 added this to Backlog in April 2017 Apr 1, 2017
@gdude2002 gdude2002 removed this from In Progress in March 2017 Apr 1, 2017
@gdude2002 gdude2002 removed this from Backlog in April 2017 May 4, 2017
@gdude2002 gdude2002 added this to Backlog in May 2017 May 4, 2017
@aramperes aramperes removed this from the 2017.3 milestone Jul 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
May 2017
Backlog
Development

No branches or pull requests

3 participants