Template talk:Bedrock Edition versions

0.12 sprite
Would it be necessary if I change the sprite for 0.12 to hunger since it's another major feature in the update, or is leaving it at the nether portal sprite more soothing --MarioProtIV (talk) 00:21, 15 July 2015 (UTC)


 * While both are major features, the Nether is likely the more anticipated feature for most users, so I would leave the portal as the icon. – KnightMiner  t/c 01:58, 15 July 2015 (UTC)

0.11 sprite
What sprite is more pleasing for 0.11?


 * Boat - current sprite
 * Fishing rod - signifies the addition of fishing (with the exclusive bobber)
 * The Player - shows the addition of skins
 * Speed particle - shows the addition of status effects
 * World boundary - shows the new ability to expand old worlds into infinite
 * Sign - the addition of languages in MCPE
 * Cave spider - addition of cave spiders
 * Squid - addition of squids and also the exclusive baby squid and "ink" cloud

Thoughts? --MarioProtIV (talk) 16:09, 7 August 2015 (UTC)

Windows 10 only updates
Because of the way some of the updates to Windows 10 are ordered, they are being placed in the same slot as the 0.x versions for MCPE, which I find misleading and inconsistent. My suggestion is either to add a section at the top for Windows 10 only updates, like this: Each 0.1x.0 version that is only on Windows 10 is in bold to not have confusion with 0.1x.0.x. Or, we could not add it, but instead create a separate template for this, shown below: Please let me know what you think. --MarioProtIV (talk) 23:02, 11 August 2015 (UTC)


 * I believe this looks much neater and is in better accordance with the style guide. TySkyo (talk) 19:54, 12 August 2015 (UTC)

{| ! Development cycle {| style="border: 0" ! Pre-release ! 0.1 !  0.2 Survival Update ! 0.3 !  0.4 !  0.5 !  0.6 !  0.7 !  0.8
 * colspan="2" |
 * colspan="2" |
 * colspan="2" |
 * colspan="2" |
 * colspan="2" |
 * colspan="2" |
 * Pre-release
 * Pre-release
 * 0.1.0
 * 0.1.1
 * 0.1.2
 * 0.1.3
 * 0.1.3
 * 0.2.0
 * 0.2.1
 * alpha 2
 * alpha 2
 * 0.3.0
 * 0.3.2
 * 0.3.3
 * 0.3.3
 * 0.4.0
 * rev 2
 * rev 2
 * 0.5.0
 * 0.5.0
 * 0.6.0
 * 0.6.1
 * 0.6.1
 * 0.7.0
 * 0.7.1
 * 0.7.2
 * 0.7.3
 * 0.7.4
 * 0.7.5
 * 0.7.6
 * 0.7.6

! 0.9
 * 0.8.1
 * 0.8.2

! 0.10
 * 0.9.1
 * 0.9.2
 * 0.9.3
 * 0.9.4
 * 0.9.5

! 0.11
 * 0.10.1
 * 0.10.2
 * 0.10.3
 * 0.10.4
 * 0.10.5

! 0.12
 * 0.11.1
 * 0.11.2


 * colspan="2" |
 * colspan="2" |
 * }
 * }


 * TySkyo@undefined What do you mean, "style guide"? Did you actually read it? It says nothing about nav box designs.
 * As for splitting, I have stated in the past that I oppose splitting them, and my mind is not changed by discussing this in a fourth place. Dinoguy has also now stated that he'd like all further discussion on this topic to be moved to MCT:PORTAL. – KnightMiner  t/c 20:31, 12 August 2015 (UTC)

"Consistent with other updates"
MarioProtIV@undefined Can you please explain how marking the Windows 10 Edition updates (and not marking any other exclusive updates), along with placing updates out of both numerical and chronological order (unlike all other updates) is "more consistent with other updates". – KnightMiner  t/c 16:12, 10 September 2015 (UTC)


 * The italics I don't really know why I did that, but for the order, it doesnt seem proper to have a minor version on top, major in the middle, and minor again at the bottom. --MarioProtIV (talk) 16:27, 10 September 2015 (UTC)


 * This conversation came to my attention as a result of your unexplained revert of my changes for the second time here.
 * @: 0.12.0 was not a minor release. In fact, 0.12.1 was built upon it and, with the addition of a proper mobile interface and other universal tweaks, was released for Windows 10 following 0.12.0. 0.12.0.1 utilized many features from the 0.12.1 beta, but still preceded the release of 0.12.1 for the Windows 10 Edition.
 * – Illidicia ( t + c ) 13:46, 29 October 2015 (UTC)


 * If there are no further objections, I will reorder the 0.12 versions by release, in ascending order. ― Illidicia ( t + c ) 20:39, 18 November 2015 (UTC)

Unneeded versions line
I honestly don't see a reason to include the "Versions" line in the version navbox, as it can simply be in the PE info template. As for PC that's different because of the way it is styled. --MarioProtIV (talk) 17:15, 4 November 2015 (UTC)


 * Because this navbox is "Pocket Edition versions", so why not include versions? It is useful enough information and fits well along side other links like the development cycle, plus the PC template includes it (of which styling is not a reason to remove the content, especially since the only differences in styling are the Computer edition has a few extra types of updates and collapsible development stages)
 * Also, if you think the other versions shouldn't be there, why do you leave the Windows 10 link? It either should say as a version, or be removed as a version, as you can hardly argue it is a separate development cycle after it getting the same 0.13.0 build as the rest of PE. – KnightMiner  t/c 04:59, 5 November 2015 (UTC)

0.15 section
Since the 0.15 builds are gonna be in two phases, I think making the 0.15 part split into two subsections, listing the builds for the Realms phase on top, while the main builds would be in the subsection below.

Thoughts? If this was put into effect, it would only be after the main builds start coming out. --MarioProtIV (talk) 21:02, 18 April 2016 (UTC)