mojira.dev

Lee Shaub

Assigned

No issues.

Reported

MCPE-24766 Win10 Hosting invisible to other devices. Cannot Reproduce MCPE-18604 MCPE 1.0 beta crash with Wifi off Duplicate MCPE-17013 Unable to exit anvil with b button Fixed MCPE-16922 MCPE .16.0 beta crashes on generating world with stronghold, then stronghold incompletely generated Duplicate MCPE-16921 MCPE .16.0 beta crashes on generating world with stronghold, then stronghold incompletely generated Duplicate

Comments

Signed one of the devices into xbox live and tried again. After playing around with it for a little, if I started the world on the server device, and then started Minecraft on my tablet, it would show up. However, if I started Minecraft on the tablet before on my pc, it would not show up till I had entirely restarted Minecraft(on my tablet)
I doubt this had much to do with xbox live.

This issue was solved quite a while ago.

None of the devices are signed into xbox live. I'm not even sure if I have a xbox account. I'll look at that though.

What devices are all of you using?
Part of the reason why this report has little attention paid to it is that there are few details regarding your hardware.

The 1.0.0.0 beta has a very long start time. On my tab(Shield K1), it takes about 5-10sec.

Happens to me on the 0.17 beta build 3, on a Shield K1 tab.
I think that it involves the new background loading of chunks. I played for about 30min, and then the game crashed, all my of progress lost. My inventory wasn't lost nor xp, but all blocks and other items/containers progress set back. Player position was set back to last save.

I'm guessing that the changes were never saved, only held in ram. Then, when the game crashed, nothing was saved.

I have had this happen to me a few times, I think it happens when there's a bit of moisture on the very edge of the touchscreen, and then seems to register as a hold on the second slot. I doubt that it's mcpe related.

Blazes will "fire up" after a little bit, but touching a blaze will not damage you. I've killed about 200 blazes, and there's no blaze rod drop.
Shield K1 Tab, Android 6.0.1, rooted, stock.

Fix confirmed for the latest beta on Nvidia Shield, 6.0.1

For some maps, it seems that if the chunk(s) that contain the stronghold are taken out of memory, the game will crash. However, if you stay around the area where the stronghold should be(i.e. close enough that the rest should be generated) and then leave the area, the game will not crash. However, when you leave the world, it will crash.