I play on the split screen as a second player and when I try to break a block it disappears, but it doesn't look like particles, and for the first player, the block is still there
and the second player he manages to cross the block that "broke"
Linked issues
is duplicated by 14
Attachments
Comments 13
in my case I can place blocks, but destroying them is not possible, the bug of MCPE-115292 he can place blocks and break them but, and I can’t break any blocks
it happens often
In my case player one are as usual.
But player two glitch or bugs.
When player two breakes a block, it disapears for player two. But doesnt collect any.
Player one wont see that the block was destroyed (its still there) and when player one then stands on the "block" or where it "was", player one stands in the "air" for player two.
If player two then place or "replace" a block where it was, it places and reforms as the original form.
Like Stone (andestit) for example. It goes to cubblestone when (If) its mined and then places as cubblestone. But not in this case as i described.
And this is Constant as soon as i/we play splitscreen.
(Sorry for my bad English, but i hope you can Read it somehow)
I have exact same issue my wife plays 2nd player she can't break blocks completely and on her screen it says she did but on my screen it shows she didn't and plus she does not collect the sand or dirt or any block for that matter
Can't mine blocks, they vanish but are still there and cause damage if stepped into.
The only thing player 2 can do is kill mobs.
Same thing is happening to us. We're on Xbox 1s playing beta and any 2nd or 3rd player that joins any world cannot break blocks or pick things up, although it does look like the block breaks when they hit it. Also, if they attempt to break a block and then stand where that block was (and still is for player 1) they'll suffocate. We're in survival and have never changed to another mode.
Same thing here for us, the 3yr old is player two and he's got it figured out at least so he doesn't die.
This might be the same issue as MCPE-115292.
Does this happen consistently, or just occasionally?