The Mineplex server in particular, and one that my friend created using the aternos host (this one in particular is what has me most distressed, since I have some friends playing on it and I ended up with my progress frozen)
I can confirm. I also noticed that other detector blocks are also broken: Tripwire hook does not activate and detector rails activate only the first time.
I do have the exact same issue and i couldn't fix it.
also we need these options in the realms.
Still happens in windows 10 (v1.1.2).
Fixed in 1.1 beta (idk the build)
Fixed in 1.1.0.8
Sad to know that. This worked well before and I built a few things that uses that mechanism.
@unknown Yes, this still happens
Relates to MCPE-18900
This still affects windows 10 edition in version 1.0. Please reopen it.
Guys their worlds were generated in version 0.16.2 or earlier, right? I have a world of 0.16.2 and when I open a copy of it in build 1 I see these errors, but when I open in build 5 (directly from 0.16.2 without having opened in other builds) I do not see these errors so I believe this has already been fixed and their worlds continue with errors because they were corrupted in build 1. I'm not sure but in this case I think mojang will not do something to fix those worlds. That's why mojang recommends backing up the worlds before installing a beta.
Fixed in 1.0.0.1
Fixed in 1.0.0.1
Still affects 1.0.0.1
Duplicate of MCPE-18488
Duplicate of MCPE-18487
Duplicate of MCPE-18370
Fixed in 1.0.0 (build 3)
I’m having the same issue, have watched countless streams, for hours and hours. And still no Home Cape code.