23rd January 2020
Minecraft News
1 0

Looks like we are still in the 1.14 beta stage, below is all the current changes added to the game. This is expected to be one of the last betas before the Minecraft developers push another bug fix release for Bedrock – We will start to head into the 1.15 Nether Update beta next hope you’re all excited.

PLEASE READ before participating in the Minecraft Beta:

  • Joining the beta will replace your game with a work in progress version of Minecraft
  • You will not have access to Realms and will not be able to join non-beta players while you’re previewing the beta
  • Any worlds played while in the beta cannot be opened in previous versions of the game so please make copies of worlds to prevent losing them
  • Beta builds can be unstable and are not representative of final version quality
  • The beta is available only on Xbox One, Windows 10, and Android (Google Play). To join or leave the beta, see aka.ms/JoinMCBeta for detailed instructions 


  • Crashes/Performance
    • Fixed several crashes that could occur during gameplay
    • Fixed a crash that could occur when searching the Marketplace
    • Fixed a crash that could occur when spawning in an item
  • General
    • Transparent blocks will no longer prevent mob spawning on the same Y axes (MCPE-59682)
      • Please note, that this fix will revert the changes made in MCPE-54241, which will require further work and will be fixed in a future update
    • Tamed Parrots will now sit on a player’s shoulder correctly after the world save is converted to Bedrock
    • Split-screen players are no longer left in a limbo split-screen state when joining the game while the primary player quits at the same time 
  • Mobs
    • Fixed an issue that prevented tamed wolves from moving towards each other to breed (MCPE-59570)
  • Items
    • The honey bottle item tooltip now says ‘Items’ instead ‘Nature’ (MCPE-61195
  • Commands
    • Beehives and nests now have the correct front texture when placed by the setblock command
    • Defining an execute location no longer breaks the use of the detect command

Comments are closed.