Just downloaded a copy locally, it behaves the same. I attached a picture of the setup, with no hopper below it works fine (except I have to manually unload the potions), but as soon as I place a hopper below the brewing stand it unloads the water bottles immediately. It does not matter whether the hopper below points at the barrel or not.
Repo is incredibly simple. Place any item on the anvil, enter a new name, there is no option to remove the item with it's new name. Philip included an image but I will add another one.
If I use the anvil to merge two items and rename, the anvil does not show the new name, and the item was not initially renamed after I took it off the anvil, but after 10 seconds or so it took on the new name. However this only works for items that can be repaired on the anvil, other items cannot be renamed.
Interesting, I left an item sitting in the anvil with the repair and name screen up and a new name entered for a while (a minute?) While entering that last comment, and eventually it showed the item in the output with the new name, and let me remove it and renamed the item. And now it seems to behave normally (without the delay) and I can no longer reproduce the problem.
Note: this is NOT just an Australia thing, I'm in Philadelphia (US east coast) and it happens here, though not every single time just half the time or so.
My complete speculation is it's a latency problem with the profanity-checker server, which would explain why it happens with all text and only on realms (since private and single player servers don't check for profanity). If it's latency related that would also explain why it is worse in AU/NZ since you're probably farther away from the server down there. Additionally I would further speculate that this profanity-checker server is likely run by a different team at Microsoft (the "Tay" team? They know something about profanity 😋) and Mojang may have no direct control over it, which would explain why this bug is "confirmed" but not fixed.
Jeff
REALMS-7725
BDS-15049
MCPE-142858
Just downloaded a copy locally, it behaves the same. I attached a picture of the setup, with no hopper below it works fine (except I have to manually unload the potions), but as soon as I place a hopper below the brewing stand it unloads the water bottles immediately. It does not matter whether the hopper below points at the barrel or not.
Repo is incredibly simple. Place any item on the anvil, enter a new name, there is no option to remove the item with it's new name. Philip included an image but I will add another one.
If I use the anvil to merge two items and rename, the anvil does not show the new name, and the item was not initially renamed after I took it off the anvil, but after 10 seconds or so it took on the new name. However this only works for items that can be repaired on the anvil, other items cannot be renamed.
Interesting, I left an item sitting in the anvil with the repair and name screen up and a new name entered for a while (a minute?) While entering that last comment, and eventually it showed the item in the output with the new name, and let me remove it and renamed the item. And now it seems to behave normally (without the delay) and I can no longer reproduce the problem.
I can repo it again after going and doing other things for a while in the game, this time the delay was 2-3 minutes before it started working.
Note: this is NOT just an Australia thing, I'm in Philadelphia (US east coast) and it happens here, though not every single time just half the time or so.
My complete speculation is it's a latency problem with the profanity-checker server, which would explain why it happens with all text and only on realms (since private and single player servers don't check for profanity). If it's latency related that would also explain why it is worse in AU/NZ since you're probably farther away from the server down there. Additionally I would further speculate that this profanity-checker server is likely run by a different team at Microsoft (the "Tay" team? They know something about profanity 😋) and Mojang may have no direct control over it, which would explain why this bug is "confirmed" but not fixed.