Confirmed in 0.13.2 (With android Samsung 10.1 combined with Amazon Kindle Fire HD 7).
This only seems to happen when using 2 more or more devices. Requires placing the redstone torch multiple times and/or removing / replacing track. Can also place an unpowered connecting track which will often cause powered track to light up.
Though I don't care for this functionality. It may be by design.
Local Multiplayer works this way as well. Hosting world on Windows 10 edition with multiple players connected (4 total) from multiple devices (some android, some IOS, various versions). All clients are disconnected when minimized.
1. Start a Windows 10 Edition world / any world (occurs in all modes) in full screen mode - must be full screen.
2. Connect to that world from another device (tested on iPhone 6, iPhone 5, Android 4.1.2 and Amazon Fire). Issue occurs with one, all or any number of those 4 connected devices.
3. On the Windows 10 (host computer), minimize the game. Can be done by pressing windows key (so you can see the task bar) and then minimize the game. Or, ALT-TAB to another active window and minimize the game. Or any other way such as showing the desktop etc.
4. Within about 1 - 2 seconds any connected clients are disconnected.
On the Windows 10 Machine, you will see a message "Player xxx left the game" and you will get that message twice for each player.
On the client device you will see the message: "Disconnected from server"
Confirmed (W10, Android Sam 5.x, Android Sam 4.x, iOS 6). However, not ALL items are invisible in Item Frames. Items I've found to be invisible so far:
Blocks of Wood (Any).
Wooden Stairs
Any stone block (Cobble, Stone, Granite, Dorite, Graven, Dirt etc. – all of them)
Wooden Fences
Any polished block
Items that definitely work:
Coal
Charcoal
Swords
Pickaxes
Flowers (any)
Seeds
Leather
Raw Meat (appears to be any)
Sticks
Diamonds
Iron Ingots
Item Frames
To clarify: You asked if it "STILL affects 0.14.2" – why would it ever stop affecting 0.14.2 unless there was an updated, which there is not? Or is there? FYI: I just a public user who installed 0.14.2 from the app store. Yes, this issue exists in the released version: 0.14.2
Confirmed: (Realm game). Same thing, a horse despawned wearing all it's armor along with about 25 cows, 10 sheep, and 30 or so chickens all de-spawned at once. This may be related to nether portals, dying in nether and re-spawning near the animal pens. Does this seem related to nether entry / exit to anyone else?
Exact same thing... both android devices. Others can connect, owner tries and it boots everyone else. If anyone finds a workmaround (othernthan a reset) please comment/update issue.
Another update: I have added the Win10 version to a PC (same account) and tried to connect. That machine cannot connect to the realm either (same messages, either "Cannot connect to world" or "disconnected from server"). Though, others are able to connect to that realm but some cannot - appears to be random, and account owner can't seem to connect from any mobile device or PC.
Another update 2: Now it would seem that any accounts who experienced this bug, can no longer host LAN games either, but can connect to other's LAN games who are not experiencing the bug. This seems very x-box live integration-centric.
It’s a bummer. But, appears to be something that's getting attention / getting worked on. Technically you're still paying for "beta" software and we're all in a trial period anyway. Looking forward to having realms be more stable. It will get there!
If you aren't ok with paying for something that might break (beta-ware), cancel your subscription. I'll keep mine open as long as this issue gets fixed in the next release.
The host is Microsoft/Mojang. And the issue you linked should be closed as all lan games now go thru your xbox account. The issue on https://bugs.mojang.com/browse/MCPE-10552 is that xbox account has been corrupted due to this issue. It has nothing to do with the local user's router settings at all.
Users have reported a new GamerTag will resolve the issue (at least for a while). So, it screams of xbox / mojang integration issues which may be why it's taking a while to sort out. I've noticed that when this occurs, LAN games no longer work for that user either. I'm pretty confident MCPE-10552 resurgence is a result of REALMS-79 / xbox mojang account integration and corruption issues. Only Mojang/Microsoft know what the cause is, or maybe they don't yet? In any case, I will resound what others have said: Some communication would be nice. Acknowledge and educate your support team as well, otherwise people are just going to keep opening tickets at best, at worst you will lose your trust relationship (that we can spend thousands of hours on a realm and not have it suddenly lost forever). Downtime is forgivable, the latter is not and will result continued use of 3rd party, hacked server/realm versions of MCPE instead.
No, I mean literally, it seems to be resolved for me at least for now. I can get into the realm again. I have been playing it since last night with no issues. I did nothing to get this working.
I did nothing. Figured they had just fixed it? If it's still broken for others, this is odd.
I did notice when I got in, I had the last few seconds of a weakness effect from fighting a witch. Maybe the glitch is related to that? I don't remember actually fighting a witch right before logging out. But, maybe I did. It was a couple of weeks ago.
The number of votes should NOT dictate the priority on issues like this.
Most people are aware that "mob farms just don't work" in MCPE. No one understands why or that it is a bug. And few people / no one can find this issue to vote on it. This should be a fairly high priority bug as a major dynamic of the game is very broken here.
Possible work around for some (but still sucks royally) and more info regarding bug:
On realms, this is is currently locking all users (including host) to a list of enchants specific to the user but potentially different from each other. For example: Pickaxes - I have Unbreaking III as the highest enchant. My wife plays on our realm and has Fortune I as the highest enchant. Again, this never changes regardless of how many enchants you do (we've done hundreds). However, we are able to get all the enchants we want by having the other people on our realm fulfill enchant requests for each other.
This is what we did:
1. Create an enchant chest for each player.
2. Put a sign above each chest with their name
3. Put another sign above that is the request sign, and the player can place their requests there.
4. Players fulfilling requests will enchant the item and then place it in the chest and take the sign down.
5. Logout and back in (utilize REALMS-91) to get XP levels back.
So long as REALMS-91 is an issue, this isn't too big of an inconvenience for other players. Hope that this is fixed before the XP bug! It makes it more bearable.
Now that I think about it, I've seen this about 5 versions ago (but not since). Seemed like it only happened while I was being blasted by a ghast. I've never had it just-happen for no reason.
My suspicion is that it may happen (have happened previously) when you are being hit by an AOE such as a ghast blast and the same blast hits a pigman. The pigman is then aggro'd to you instead of the ghast which is like 80 blocks away / too far to be aggro'd. I'll test this in the next couple of days and respond back.
As @Rob Russin said: This is an issue with modelling and that's all. Just to repeat, so everyone is aware of the work around: Once the wart appears full grown, wait for it to appear just planted (small) again and then harvest. You'll get your multiple warts instead of just the one!
No one expects hard dates. But Majong's kanban/agile hybrid flavor of sprint management which is non-standard to the rest of world tends to frustrate both your tech and non-tech savvy user base. You should consider at least assigning bugs and making your current sprint items visible to the public. Your stories are all cluttered with user comments similar to what @Mat Cooke just asked.
Isn't there a hostile mob limit per loaded chunk? I seem to remember seeing this on the wiki years ago, now I can't find it. I want to say it was 256. And btw: that is an insane number for most mobile devices.
I have a railroad track built 100% on half slabs 4 blocks below the build limit. All blocks within 1000 spaces horizontally and 60 vertically are half slabs. Hostile mobs spawn on it. Also, I have a roof that is 100% half slabs and my nearby golem farm spawns golems on it. Not sure if golems are considered hostile or passive.
[MCPE Mod] Mega_Spud Appreciate you attempting to provide specific insights like this and as you have done on other issues, like linking to Mojang's twitter page. Would be nice if mojang provided some visibility into what issues they are working on, instead of relying on moderators to be the professionals.
I don't see how that proves it's working. Stand on top of your donut-shaped mob spawner in the ocean and go straight up, 25-35 blocks from the center. Nothing will spawn, even with 0 mobs in the vicinity. I have personally tried this.
Also, couple the aforementioned mentioned fact with this:
I have a mine-cart track sitting at the build height limit in a plains zone which goes 2k blocks in one direction. The plains sit at about sea-level (about 62z) and my track is at 126z (just below build limit) on half-slabs. I get mobs spawning below me on the ground at / about 24-36 blocks either Y or X in-front or behind me constantly. I can sit up there on my track and shoot at them, kill them and watch more spawn.
The game doesn't take into account your z axis for mob spawns and possibly despawns and that seems pretty clear. I believe this relates to at least 3 other issues as well.
Thanks, you are to be commended for providing an update! It is really appreciated! But, to me this comment implies most confirmed bugs aren't important enough to your team to make it into your internal tracker. Why did this bug make it and others didn't? You see how this perception makes us think we are all wasting our time here?
Confirmed in 0.13.2 (With android Samsung 10.1 combined with Amazon Kindle Fire HD 7).
This only seems to happen when using 2 more or more devices. Requires placing the redstone torch multiple times and/or removing / replacing track. Can also place an unpowered connecting track which will often cause powered track to light up.
Samgsung 10.1 HD, Windows 10 confirmed as well.
Also, an item at the end of your inventory list will be permanently lost when this bug occurs.
Though I don't care for this functionality. It may be by design.
Local Multiplayer works this way as well. Hosting world on Windows 10 edition with multiple players connected (4 total) from multiple devices (some android, some IOS, various versions). All clients are disconnected when minimized.
1. Start a Windows 10 Edition world / any world (occurs in all modes) in full screen mode - must be full screen.
2. Connect to that world from another device (tested on iPhone 6, iPhone 5, Android 4.1.2 and Amazon Fire). Issue occurs with one, all or any number of those 4 connected devices.
3. On the Windows 10 (host computer), minimize the game. Can be done by pressing windows key (so you can see the task bar) and then minimize the game. Or, ALT-TAB to another active window and minimize the game. Or any other way such as showing the desktop etc.
4. Within about 1 - 2 seconds any connected clients are disconnected.
On the Windows 10 Machine, you will see a message "Player xxx left the game" and you will get that message twice for each player.
On the client device you will see the message: "Disconnected from server"
Duplicate issue: https://bugs.mojang.com/browse/MCPE-14136
Confirmed (W10, Android Sam 5.x, Android Sam 4.x, iOS 6). However, not ALL items are invisible in Item Frames. Items I've found to be invisible so far:
Blocks of Wood (Any).
Wooden Stairs
Any stone block (Cobble, Stone, Granite, Dorite, Graven, Dirt etc. – all of them)
Wooden Fences
Any polished block
Items that definitely work:
Coal
Charcoal
Swords
Pickaxes
Flowers (any)
Seeds
Leather
Raw Meat (appears to be any)
Sticks
Diamonds
Iron Ingots
Item Frames
MCPE-14238doesn't have 0.14.2 as a version.Please advise, how to approach that scenario for reporting. Thanks!
What do you mean "still affects 0.14.2"? Is there a patch to this version?
Sorry...
To clarify: You asked if it "STILL affects 0.14.2" – why would it ever stop affecting 0.14.2 unless there was an updated, which there is not? Or is there? FYI: I just a public user who installed 0.14.2 from the app store. Yes, this issue exists in the released version: 0.14.2
No worries. I'm, a little new to this and wasn't sure if I missed something.
Verified on 0.14.2
It is not widely understood why mob farms don't work on MCPE. People on the forums just assume MCPE is different / sucks.
Duplicate of: https://bugs.mojang.com/browse/MCPE-14136
Moderators, please link close. Users, please vote for https://bugs.mojang.com/browse/MCPE-14136
Shouldn't we close: https://bugs.mojang.com/browse/MCPE-14161
and https://bugs.mojang.com/browse/MCPE-14371
?
Funny how many people will comment to say "I have this issue" but not vote?
Chad and Andy - you should utilize the vote button on the upper right of page.
Confirmed: (Realm game). Same thing, a horse despawned wearing all it's armor along with about 25 cows, 10 sheep, and 30 or so chickens all de-spawned at once. This may be related to nether portals, dying in nether and re-spawning near the animal pens. Does this seem related to nether entry / exit to anyone else?
Also, starting/stopping realm made no difference
Exact same thing... both android devices. Others can connect, owner tries and it boots everyone else. If anyone finds a workmaround (othernthan a reset) please comment/update issue.
Another update: I have added the Win10 version to a PC (same account) and tried to connect. That machine cannot connect to the realm either (same messages, either "Cannot connect to world" or "disconnected from server"). Though, others are able to connect to that realm but some cannot - appears to be random, and account owner can't seem to connect from any mobile device or PC.
Another update 2: Now it would seem that any accounts who experienced this bug, can no longer host LAN games either, but can connect to other's LAN games who are not experiencing the bug. This seems very x-box live integration-centric.
Verified on 0.15.1
Please update.
Resurgence of this issue may be related to: https://bugs.mojang.com/browse/REALMS-79
After that bug occurs, it breaks the ability to connect to any LAN games as well.
This is a duplicate of: https://bugs.mojang.com/browse/REALMS-79
Please comment on that issue and vote / watch it. A moderator will close this as a duplicate issue.
Related to https://bugs.mojang.com/browse/REALMS-79 ?
It’s a bummer. But, appears to be something that's getting attention / getting worked on. Technically you're still paying for "beta" software and we're all in a trial period anyway. Looking forward to having realms be more stable. It will get there!
If you aren't ok with paying for something that might break (beta-ware), cancel your subscription. I'll keep mine open as long as this issue gets fixed in the next release.
Tokes,
Is there a player.dat file on the client device?
The host is Microsoft/Mojang. And the issue you linked should be closed as all lan games now go thru your xbox account. The issue on https://bugs.mojang.com/browse/MCPE-10552 is that xbox account has been corrupted due to this issue. It has nothing to do with the local user's router settings at all.
Users have reported a new GamerTag will resolve the issue (at least for a while). So, it screams of xbox / mojang integration issues which may be why it's taking a while to sort out. I've noticed that when this occurs, LAN games no longer work for that user either. I'm pretty confident
MCPE-10552resurgence is a result ofREALMS-79/ xbox mojang account integration and corruption issues. Only Mojang/Microsoft know what the cause is, or maybe they don't yet? In any case, I will resound what others have said: Some communication would be nice. Acknowledge and educate your support team as well, otherwise people are just going to keep opening tickets at best, at worst you will lose your trust relationship (that we can spend thousands of hours on a realm and not have it suddenly lost forever). Downtime is forgivable, the latter is not and will result continued use of 3rd party, hacked server/realm versions of MCPE instead.Just me or is this resolved now for others as well?
At least for the time being...
No, I mean literally, it seems to be resolved for me at least for now. I can get into the realm again. I have been playing it since last night with no issues. I did nothing to get this working.
I did nothing. Figured they had just fixed it? If it's still broken for others, this is odd.
I did notice when I got in, I had the last few seconds of a weakness effect from fighting a witch. Maybe the glitch is related to that? I don't remember actually fighting a witch right before logging out. But, maybe I did. It was a couple of weeks ago.
The number of votes should NOT dictate the priority on issues like this.
Most people are aware that "mob farms just don't work" in MCPE. No one understands why or that it is a bug. And few people / no one can find this issue to vote on it. This should be a fairly high priority bug as a major dynamic of the game is very broken here.
0.15.2... still an issue.
Possible work around for some (but still sucks royally) and more info regarding bug:
On realms, this is is currently locking all users (including host) to a list of enchants specific to the user but potentially different from each other. For example: Pickaxes - I have Unbreaking III as the highest enchant. My wife plays on our realm and has Fortune I as the highest enchant. Again, this never changes regardless of how many enchants you do (we've done hundreds). However, we are able to get all the enchants we want by having the other people on our realm fulfill enchant requests for each other.
This is what we did:
1. Create an enchant chest for each player.
2. Put a sign above each chest with their name
3. Put another sign above that is the request sign, and the player can place their requests there.
4. Players fulfilling requests will enchant the item and then place it in the chest and take the sign down.
5. Logout and back in (utilize
REALMS-91) to get XP levels back.So long as
REALMS-91is an issue, this isn't too big of an inconvenience for other players. Hope that this is fixed before the XP bug! It makes it more bearable.This is a duplicate of this: https://bugs.mojang.com/browse/REALMS-91
Could a moderator please update either
MCPE-14253orREALMS-91? Also, version should include 0.15.40.15.4 confirmed....
As a side note, this makes golem farms work better than normal. There's always a silver lining!
Now that I think about it, I've seen this about 5 versions ago (but not since). Seemed like it only happened while I was being blasted by a ghast. I've never had it just-happen for no reason.
My suspicion is that it may happen (have happened previously) when you are being hit by an AOE such as a ghast blast and the same blast hits a pigman. The pigman is then aggro'd to you instead of the ghast which is like 80 blocks away / too far to be aggro'd. I'll test this in the next couple of days and respond back.
As @Rob Russin said: This is an issue with modelling and that's all. Just to repeat, so everyone is aware of the work around: Once the wart appears full grown, wait for it to appear just planted (small) again and then harvest. You'll get your multiple warts instead of just the one!
@[Mojang] MissMarzenia (Aleksandra Zajac)
No one expects hard dates. But Majong's kanban/agile hybrid flavor of sprint management which is non-standard to the rest of world tends to frustrate both your tech and non-tech savvy user base. You should consider at least assigning bugs and making your current sprint items visible to the public. Your stories are all cluttered with user comments similar to what @Mat Cooke just asked.
This site is for MCPE issues and majong/ms won't support systems that have been modded.
While I have experienced this personally, it's NOT a bug with MCPE, it's an issue with the pocket editor. Maybe try reporting it to them.
Confirmed on 0.15.4 in all modes and realms.
Note: Mushrooms will propagate in daylight on podzol. But, they will not grow into giant mushrooms @[MCPE Mod] rplatham 's conclusion seems correct.
Isn't there a hostile mob limit per loaded chunk? I seem to remember seeing this on the wiki years ago, now I can't find it. I want to say it was 256. And btw: that is an insane number for most mobile devices.
I have a railroad track built 100% on half slabs 4 blocks below the build limit. All blocks within 1000 spaces horizontally and 60 vertically are half slabs. Hostile mobs spawn on it. Also, I have a roof that is 100% half slabs and my nearby golem farm spawns golems on it. Not sure if golems are considered hostile or passive.
This is a duplicate...
[MCPE Mod] Mega_Spud Appreciate you attempting to provide specific insights like this and as you have done on other issues, like linking to Mojang's twitter page. Would be nice if mojang provided some visibility into what issues they are working on, instead of relying on moderators to be the professionals.
This perception is sad because it's true.
I don't see how that proves it's working. Stand on top of your donut-shaped mob spawner in the ocean and go straight up, 25-35 blocks from the center. Nothing will spawn, even with 0 mobs in the vicinity. I have personally tried this.
Also, couple the aforementioned mentioned fact with this:
I have a mine-cart track sitting at the build height limit in a plains zone which goes 2k blocks in one direction. The plains sit at about sea-level (about 62z) and my track is at 126z (just below build limit) on half-slabs. I get mobs spawning below me on the ground at / about 24-36 blocks either Y or X in-front or behind me constantly. I can sit up there on my track and shoot at them, kill them and watch more spawn.
The game doesn't take into account your z axis for mob spawns and possibly despawns and that seems pretty clear. I believe this relates to at least 3 other issues as well.
@nighter
Thanks, you are to be commended for providing an update! It is really appreciated! But, to me this comment implies most confirmed bugs aren't important enough to your team to make it into your internal tracker. Why did this bug make it and others didn't? You see how this perception makes us think we are all wasting our time here?