Luke
- Lucca_BRA
- lucca_bra
- Europe/Stockholm
- Yes
- No
BDS-13573
MCPE-134538
After the 1.17 update, /kick command doesn't work with target selectors anymore. This completely ruined moderation on realms and BDS servers, since we can no longer ban players. Before the update, we would simply do /kick @a[tag=banned] in a repeating command block and assign the tag to anyone we'd like to ban from our realms/BDS servers and now we can't anymore.
It is now impossible to run a public BDS server (my case) without being able to ban players (since BDS software also doesn't offer this feature). Please fix this issue and roll it back to how it was before the update, since there is no reason to remove this feature at all...
Please don't ruin
withservercreators' lifes! Thank you..After the 1.17 update, /kick command doesn't work with target selectors anymore. This completely ruined moderation on realms and BDS servers, since we can no longer ban players. Before the update, we would simply do /kick @a[tag=banned] in a repeating command block and assign the tag to anyone we'd like to ban from our realms/BDS servers and now we can't anymore.
It is now impossible to run a public BDS server (my case) without being able to ban players (since BDS software also doesn't offer this feature). Please fix this issue and roll it back to how it was before the update, since there is no reason to remove this feature at all...
Please don't ruin public server and realms! Thank you..
When the player has the "mute" ability, obtainable by doing the command /ability <player> mute true the game automatically disables the chat ability as well as commands like /titleraw and /tellraw so the player can't use them to bypass the mute, which is understandable. However, these commands should work when executed by the player inside a function, as this way they couldn't be used to bypass the mute as they are inside a function in the behavior pack of the world.
The reason i'm reporting this bug is because it breaks many of my systems of custom items, which runs a function containing /titleraw commands at the player who clicks on the item.Steps to reproduce:
- Create a behavior pack with a function containing the command +/titleraw @s title {"rawtext":[ {"text":"This is a test"}
]}+.
- Apply the behavior pack to a world and join the world.
- Mute yourself using the command /ability @s mute true.
- Run the function containing the /titleraw using /function <name/path>.
Expected results: The title saying "This is a test" should be displayed to the player as the /titleraw is inside a function.
Actual results: The title saying "This is a test" doesn't show.Thank you!
When the player has the "mute" ability, obtainable by doing the command /ability <player> mute true the game automatically disables the chat ability as well as commands like /titleraw and /tellraw so the player can't use them to bypass the mute, which is understandable. However, these commands should work when executed by the player inside a function, as this way they couldn't be used to bypass the mute as they are inside a function in the behavior pack of the world.
The reason i'm reporting this bug is because it breaks many of my systems of custom items, which runs a function containing /titleraw commands at the player who clicks on the item.Steps to reproduce:
- Create a behavior pack with a function containing the command +/titleraw @s title {"rawtext":[ {"text":"This is a test"}
+
]}.
- Apply the behavior pack to a world and join the world.
- Mute yourself using the command /ability @s mute true.
- Run the function containing the /titleraw using /function <name/path>.
Expected results: The title saying "This is a test" should be displayed to the player as the /titleraw is inside a function.
Actual results: The title saying "This is a test" doesn't show.Thank you!
When the player has the "mute" ability, obtainable by doing the command /ability <player> mute true the game automatically disables the chat ability as well as commands like /titleraw and /tellraw so the player can't use them to bypass the mute, which is understandable. However, these commands should work when executed by the player inside a function, as this way they couldn't be used to bypass the mute as they are inside a function in the behavior pack of the world.
The reason i'm reporting this bug is because it breaks many of my systems of custom items, which runs a function containing /titleraw commands at the player who clicks on the item.Steps to reproduce:
- Create a behavior pack with a function containing the command +/titleraw @s title {"rawtext":[ {"text":"This is a test"}
+
]}.
- Apply the behavior pack to a world and join the world.
- Mute yourself using the command /ability @s mute true.
- Run the function containing the /titleraw using /function <name/path>.
Expected results: The title saying "This is a test" should be displayed to the player as the /titleraw is inside a function.
Actual results: The title saying "This is a test" doesn't show.Thank you!
When the player has the "mute" ability, obtainable by doing the command /ability <player> mute true the game automatically disables the chat ability as well as commands like /titleraw and /tellraw so the player can't use them to bypass the mute, which is understandable. However, these commands should work when executed by the player inside a function, as this way they couldn't be used to bypass the mute as they are inside a function in the behavior pack of the world.
The reason i'm reporting this bug is because it breaks many of my systems of custom items, which runs a function containing /titleraw commands at the player who clicks on the item.Steps to reproduce:
- Create a behavior pack with a function containing the command +/titleraw @s title {"rawtext":[ {"text":"This is a test"}
]}+.
- Apply the behavior pack to a world and join the world.
- Mute yourself using the command /ability @s mute true.
- Run the function containing the /titleraw using /function <name/path>.
Expected results: The title saying "This is a test" should be displayed to the player as the /titleraw is inside a function.
Actual results: The title saying "This is a test" doesn't show.Thank you!
When the player has the "mute" ability, obtainable by doing the command /ability <player> mute true the game automatically disables the chat ability as well as commands like /titleraw and /tellraw so the player can't use them to bypass the mute, which is understandable. However, these commands should work when executed by the player inside a function, as this way they couldn't be used to bypass the mute as they are inside a function in the behavior pack of the world.
The reason i'm reporting this bug is because it breaks many of my systems of custom items, which runs a function containing /titleraw commands at the player who clicks on the item.Steps to reproduce:
- Create a behavior pack with a function containing the command
+/titleraw @s title {"rawtext":[ {"text":"This is a test"}]}
+.
- Apply the behavior pack to a world and join the world.
- Mute yourself using the command /ability @s mute true.
- Run the function containing the /titleraw using /function <name/path>.
Expected results: The title saying "This is a test" should be displayed to the player as the /titleraw is inside a function.
Actual results: The title saying "This is a test" doesn't show.Thank you!
/titleraw and /tellraw doesn't workeven in functions when the player executing the functionhas the "mute" ability/titleraw and /tellraw commands doesn't work if the player has the "mute" ability
When the player has the "mute" ability, obtainable by doing the command /ability <player> mute true the game automatically disables the chat ability as well as commands like /titleraw and /tellraw so the player can't use them to bypass the mute, which is understandable. However, these commands should work when executed by the player inside a function, as this way they couldn't be used to bypass the mute as they are inside a function in the behavior pack of the world.
The reason i'm reporting this bug is because it breaks many of my systems of custom items, which runs a function containing /titleraw commands at the player who clicks on the item.Steps to reproduce:
- Create a behavior pack with a function containing the command /titleraw @s title {"rawtext":[ {"text":"This is a test"}
]}.
Apply the behavior pack to aworld and join the world.- Mute yourself using the command /ability @s mute true.
- Run the function containing the /titleraw using /function <name/path>.
Expected results: The title saying "This is a test" should be displayed to the player as the /titleraw is inside a function.
Actual results: Thetitle saying "This is a test" doesn't show.Thank you!
When the player has the "mute" ability, obtainable by doing the command /ability <player> mute true, the /titleraw and /tellraw does not work, but others do. However, these commands should work as there's no way to use them to bypass the mute, as they're commands that are only available for players with the Operator permission, which also allows them to do +/ability @s mute false+ and disable the mute.
The reason i'm reporting this bug is because it breaks many of my systems of custom items, which runs a function containing /titleraw commands at the player who clicks on the item.
Steps to reproduce:
- Create a new world and join it.
- Mute yourself using the command /ability @s mute true.
- Run a /tellraw or /titleraw command.
Expected results: The command works normally as other commands work.
Actual results: The command doesn't work and a message appears saying "Chat is currently disabled".Thank you!
So, I'm tired of waiting, so I just removed all the buildings in the affected area and I'm rebuilding everything again, I think it will take less time than waiting until June for the bug fix.
Oof, lol ok. Well then thank you and sorry for that, I searched for it and didn't find anything so that's why I thought it was a bug :facepalm:
It has been solved for me in the new hotfix released yesterday
Now this bug is getting fixed in 4 days. In 6 months that issue is happening, I rebuilt the destroyed part of my world, built a giant skyscraper, opened a RP server on that city and now I'm building another one. That was very disrespectful for people who lost most of their world. I was lucky to have only 5-8 chunks destroyed.
I really don't understand how you guys can leave an issue of this size unfixed for 1 fricking year. (Yes, I have this issue since the day 1 when Bedrock was released on Ps4). Just put old and big issues like this in the top of the list instead of fixing small issues every update... The stupid button hold thing doesn't work for most people (like me) and having to reinstall the game every day is not a possibility for people who have slow internet connections (like me). I paid for a game and every time I want to play that game I get stressed instead of relaxed...
I'm having this issue, but when using /tp to teleports players to distant Y coordinates. For example, teleporting an a player from y=90 to y=30 and vice-versa.
PLEASE VOTE FOR THE ISSUE ABOVE ^^ (MCPE-130250)**
I've had this issue on my previous server, which i had to entirely delete because of these tickingareas causing extremely high RAM usage. Not sure if this is still an issue, but if the devs did nothing then it probably is. I'm now scared of making my server non-whitelisted again because of hackers who might spawn agents and create the issue again.
Hello! Yes that makes sense now. I reported this because the issue i am having is with a custom item that runs /titleraw and /tellraw commands when the players click on the item. The /titleraw and /tellraw that are supposed to run when the player clicks the item doesn't work when they're muted, but should work as they're not being ran directly by the player, but by an addon that is running the command as the player. It works on command blocks, but not when ran by addons. That's what i meant to report haha.