Closed cssbz closed 3 years ago
Thank you so much for the detailed report! Developers love that stuff. However, you're on an older Geyser build - this error has since been fixed; please download a newer build (and the one recommendation I would give is, if possible, to always update to the latest build of a plugin before reporting an error). The problem was a regression where we weren't handling Java -> Bedrock identifiers correctly if they were the same between the two platforms. Thanks for reporting anyway!
Ooof! Thanks for the friendly reply!
Describe the bug
The following commands differ only in the CanPlaceOn restriction. The first specifies a stone block which can only be placed on pink_wool, and this operates as expected. The second, where the stone block can only be placed on dirt, produces an invisible item from the Bedrock player's point of view.
To Reproduce
OK:
/give .RubyNine3296661 minecraft:stone{CanPlaceOn:["minecraft:pink_wool"]}
CanPlaceOn
restriction operating as expected.FAIL:
/give .RubyNine3296661 minecraft:stone{CanPlaceOn:["minecraft:dirt"]}
... Gave 1 [Stone] to .RubyNine3296661
message. There is no other apparent change on the screen - there are no animations, and the hand and hotbar remain unchanged. However, it seems that actually an invisible stone block has been received. If the hotbar slot containing this invisible item is selected, the Bedrock player can attempt to place it. TheCanPlaceOn
restriction operates as expected, but only the use of the item is visible: when the stone block is placed, it is visible, but it is never visible in the hotbar or hand.I've also found a similar issue with CanDestroy and these items:
This may not be quite the same issue... in the FAIL case here, the pickaxe is invisible (as with the stone block above), but it also seems that the pickaxe can't be used.
I've found these particular problematic
CanPlaceOn
/CanDestroy
combinations by boiling down issues in two mini games. I have noticed that the OK cases here refer to items containing the underscore character, whereas the FAIL cases don't contain that character. I don't know if that's the case generally - I haven't looked for other similar cases, but I assume they will exist.Expected behaviour
Please see the To Reproduce section.
Screenshots / Videos
No response
Server Version and Plugins
On this server, when I type
/version
in the Java or Bedrock client, I see "The server is running CraftBukkit version 3180-Spigot-38e6c03-ca0fe5b (MC: 1.17.1) (Implementing API version 1.17.1-R0.1-SNAPSHOT)".I'm not the server owner and don't know all the details. Geyser is running in a Bungee proxy server. The owner has run
/geyser dump
- details below. I do know the owner well and can supply more detail if requested.I do know that we isolated this bug on 18/07/2021, with an installed Geyser version from a few days before. We then updated Geyser on that day to the current version, and the issue persisted.
NB for the "Geyser Version" field in this bug report form below, I've found that detail from the Geyser Dump.
Geyser Dump
https://dump.geysermc.org/PjWiD0LsdOlUClvfn5cHzLim30HwTa72
Geyser Version
1.4.1-SNAPSHOT (git-master-0e72952)
Minecraft: Bedrock Edition Version
v1.17.10
Additional Context
The server owner has seen this error in the console (from the bungee proxy I believe), whilst I was testing.