MetalManiac
- MetalManiac
- metalmaniac
- Europe/Paris
- Yes
- No
MCPE-120228
Confirmed for 1.17.1.01
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying {{player.json
- add }}a test to check if the player has stopped moving
- link it to an event to run a command when activated { }
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying {{player.json
- add}}a test to check if the player has stopped moving
- link it to an event to run a command when activated{}
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying {{player.json]]
- adda test to check if the player has stopped moving
- link it to an event to run a command when activated{}
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying{{player.json]]
- adda test to check if the player has stopped moving
- link it to an event to run a command when activated{}
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json
- add a test to check if the player has stopped moving
-link it to an event to run a command when activated
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated
- Activate it and run around
Observed Results:{}
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated
- Activate it and run around
Observed Results:{}
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json, or use the player.json
.
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json, or use the player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json, or use the player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
The behavior pack is_moving filter randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
Iwill try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json, or use the
player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
The behavior pack is_moving filter/query randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I have been told in that was an issue since the 1.15s, but we can go around it using the modified_move_speed query.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json, or use the player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
is_moving filter & query randomly cuts
The behavior pack is_moving filter/query randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I have been told in that was an issue since the 1.15s, but we can go around it using themodified_move_speed query.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json, or use the player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
The behavior pack is_moving filter/query randomly outputs false for a short time even when the player is moving for an extended period of time.
More precisely, during the player movement, if is_moving is continuously called upon, it will sometimes, randomly return that the player in not moving. This happens more commonly during sprints.
I have been told in that was an issue since the 1.15s.
I will try to have a video attached sometime soon.Steps to Reproduce:
- Create a behavior pack modifying player.json, or use the player.json
- add a test to check if the player has stopped moving
- link it to an event to run a command when activated- Activate it and run around
Observed Results:
- The command will eventually randomly run while you are movingExpected Results:
- It should only run when the player stops moving
Video attached! Sorry for the quality
Please remember that this is a bug tracker and not a forum for discussion or feedback. Please keep any comments limited to NEW, relevant information about the bug only, and add a vote if you would like to show your interest in this issue. Off-topic comments and chatter may be hidden to avoid clutter, enabling us to focus on the information relevant to the bug.
While we understand your frustration at certain game feature or mechanics not working as you would always like or expect, please remember that there is not always a simple fix that will resolve the issue immediately. Please be assured we are actively looking into a solution though.
For further discussion and community feedback please visit one of the following websites:
For any support issues, please contact Minecraft Customer Support directly.
Furthermore, @JP please stop asking these questions until you yourself know how to code your way around the glitchy and crumbly PlayStation and hypersensative C++.
Please read the Mojang-Microsoft logs. There is a PS crash stopping Microsoft accounts to connect to the internet right niw. They don't know when it'll be fixed
Entirely sure. I even tried the latest beta, uninstalling and reinstalling the game multiple times, deleting add-ons... Yup it definitly is a thing.
Same on Android 8.1.0 but the freeze never stops. A further information about the freeze: chunks don't load.
It has nothing to do with mobs btw for me. It just happens after a few seconds in-game.
All worlds are corrupted for me. I'll send a world soon
Corruptedworld.zip
Here you go for a world.
8.1.0 for me
Seems to be fixed. Probably linked to
MCPE-123234...It fixed for me. Not even after a specific update. It seems to be linked to
MCPE-120228as both appeared and got fixed at the same time.Nuh, doesn't work for me either.
Confirmed for 1.16.230.56 beta.
Confirmed for 1.16.221
Confirmed for 1.17.0.50
Not related to BDSs
I can smelt none of the raw ores. I don't know if only these or all smelting is broken. I'll check.
Confirmed for 1.17.1.01
Confirmed for 1.17.1.
Does it work in your old worlds too ?
By the way to the one editing the wiki we can not say this bug is fixed until the bug report is closed.
This is not the same bug. The one you are talking about happens with about every platform connecting with a Switch. Here we are talking about PS4 users that can't join or be joined by any platform. Feel free to vote for the correct bug report though.
It still is in issue in 1.17.2.01.
A lot of semitransparent textures are quirky like that.
Can confirm it has been recentlyish fixed, it was a global Bedrock multiplayer bug.
I wonder if you wan fix this by adding a texture to the light_block in terrain_textures.json...
I'm pretty sure this comes from the pack, not the game
That's the same problem as with world icons as the game can't take raytraced pictures
Mojira helpers are the best.
Hmm I had searched thoroughly for a duplicate and hadn't found one, that's weird...
Updated and fixed
Still an issue in 1.19.0, both for downloads started before and after the update.
I'll check as soon as I can.
Fixed in beta 1.19.20.24
Similar issues with French.
The translators have been informed. And GG for playing in Shakespearian!
This is not actually the same bug, I have checked the report, my eyes did not disappear from the character but were replaced.
Created a seperate bug report here
MCPE-165570