mojira.dev

Zhuowei Zhang

Assigned

No issues.

Reported

MCPE-39297 .mcworld, mcpack, and mcaddon files with ampersand in name won't import Works As Intended MCPE-37160 Vibrate on block destroy doesn't work in Survival Fixed MCPE-25227 Preview screenshot in world select menu glitched Fixed MCPE-25225 Upgrading to Android 8.0.0 causes black screen at startup until ShaderCache2 is deleted Fixed MCPE-22195 Touches are stuck after backgrounding game by pressing home button Fixed MCPE-17693 Force close if Android app backgrounded while loading textures at startup Invalid MCPE-14229 "Tap Jump to Exit Minecart" message missing in Realms beta, 0.14.2 Cannot Reproduce MCPE-10203 Phantom local server in world list after exiting world Duplicate MCPE-8464 Back button on Android navbar doesn't work in Options menu Fixed MCPE-8394 Segfault when low memory event fires Fixed MCPE-8266 Crash after exiting app: null pointer exception in isNetworkEnabled Fixed MCPE-7091 CompoundTag::putLong has wrong parameter type (should be long long, not long) Fixed MCPE-6412 Force-close when app is closed: segfault in AppPlatform::_fireAppSuspended() Cannot Reproduce MCPE-1052 Minecraft Raspberry PI API is compiled for Java 7 only Invalid MCPE-537 Chests do not remove items with invalid item IDs loaded from saves Cannot Reproduce

Comments

Can reproduce on Google/Huawei Nexus 6P, Android 8.1, Minecraft 1.9.0.3 beta.

 

My symptoms are the same as MCPE-39428: sometimes, when entering a world, all blocks are black (in inventory, in hand, and in the world). Items and mobs render normally. This happens about once in 20 times.

[media]

[media]

Exiting and reopening the world fixes the issue. Backgrounding and then resuming Minecraft also fixes the issue.

Still occurs on 1.9.0.0 Beta.

This seems to be fixed in 1.6.0 release (Nexus 6P, Android 8.1.0): worlds opened on 1.6.0 shows non-glitched screenshots; worlds that were never opened on 1.6.0 still had glitched previews.

Still reproducing on 1.2.0 release.

Still reproducing on 1.2.0 full release. (why...)

Still reproducing on 1.2.0.25.

@SuperGeniusZeb I can't trigger it on 1.2.0b22 on a Nexus 6P anymore, but maybe that device is too fast; I can check on the Nexus 7 again if you want.

Manually deleting the cache/minecraftpe/ShaderCache2 folder also fixes the problem. It seems that Minecraft PE doesn't invalidate the shader cache on OS upgrade.

Can confirm: Minecraft PE 1.12.0.18, Android 8.0.0, Nexus 6P

I can't reproduce 1 and 3, but I can reproduce a crash when cancelling an Xbox Live signin. Android 7.1.2, Nexus 6P, Minecraft 1.2.0.18

Can confirm: Android 7.1.2, Nexus 6P, 1.2.0.18.

Can confirm: Minecraft PE 1.0.5.0, Android 7.1.1 on Nexus 6P, Gboard 6.1.71.149620197-arm64-v8a

Can confirm: running 1.0.5.0 on Nexus 6P/Android 7.1.1.

Still affects 0.17.0 alpha build 1 when using Left Handed mode: I'm on a Nexus 6P running Android 7.0.

Looks like GameMode::startDestroyBlock isn't being called; that function is responsible for calling Level::extinguishFire to put out the fire when you punch a block in Survival.

Confirmed in 0.7.2 (Android from Google Play, same Nexus 7 as before)

Confirmed Android 0.7.1, Asus Nexus 7, Android 4.2.2, and made a patch that fixes it for Android. It's available on my mod thread.

The source of the bug is embarrassingly simple: Mojang typed a 0 instead of a 1.

They based the fire behaviour on Minecraft 1.5, which had the line of code

Block.TNT.postBreak(world, i, j, k, 0);

However, TNT was ported from a later Desktop release, which meant that the line of code was supposed to be

Block.TNT.postBreak(world, i, j, k, 1);

(method names are from Bukkit on the desktop edition)

The relevant function is in FireTile::checkBurn.

Mojang fail level: 0... I mean 1.

Confirmed, and made a patch that fixes it for Android. It's available on my mod thread.

The source of the bug is embarrassingly simple: Mojang typed a 0 instead of a 1.

Block.TNT.postBreak(world, i, j, k, 0);

Since they based the fire behaviour on Minecraft 1.5

When they should've typed

Block.TNT.postBreak(world, i, j, k, 1);

Which is Desktop Edition 1.6 and above's code, used to port TNT.

(method names are from Bukkit on the desktop edition)

The relevant function is in FireTile::checkBurn.

Mojang fail level: 0... I mean 1.

Confirmed on Nexus 7 running stock firmware as well.

I can reproduce as well - Android 4.0, Toshiba Thrive, MCPE 0.6.1 without any mods patched from Google Play.

Steps to reproduce:

  • Open a world

  • Close a door

  • save and exit

  • open that world again

  • door is open again

Steps to avoid the problem:

  • Close/open a door

  • place or destroy any block

  • save and exit

  • door saves status