![]() |
VOOZH | about |
Would it be worthwhile to add a parameter to link to a version article? Possibly even change the title based on that. With the new page system, it seems that Upcoming features' usage is becoming less and instead 1.8 would be the page to link to. --KnightMiner (t|c) 20:45, 16 August 2014 (UTC)
Currently, if a feature is upcoming to both Java and Bedrock editions, they will have this: {{Upcoming|1.9|1.14}}. However, this creates confusions, like: "What? The current version is 1.13, but it is still upcoming to 1.9? And they are upcoming to 1.14 as well?" So we should think of some way to clear this out.
Below are my two ways of doing this:
{{upcoming|Bedrock Edition 1.9}} already has a tooltip; hovering over '1.9' shows "Bedrock Edition 1.9". And I think it's fine as-is, if you're confused just click the link. That's what it's there for. – Nixinova 👁 ImageWhat's the difference between this template and Template:OnlyUpcoming? They both appear to have the same purpose, just this one is older and more widely used.
Thanks, PurPur13 (talk) 01:09, 24 November 2023 (UTC)
For example, this uses upcoming (on the lava chicken thing), but this uses another table (Upcoming Java Edition). Stysan (talk) 20:29, 25 June 2025 (UTC)
I've noticed that it gets hard to update pages after a drop releases sometimes because the categories aren't precise, might be 26.30, 26.40, can be Chaos Cubed, Third Drop 2026, etc. I'm trying to think of a way to alleviate this prob◙8em and was wondering if there was any other ideas. 👁 Image
FireDragons52 07:59, 12 June 2026 (UTC)
[[Category:{{#titleparts:{{#var:$version}} upcoming}}]] would work for this, though it would take a bit more to make sure it only works if used with a version parameter and so it doesn't output "BE 26.40"/"Bedrock 26.40" instead of "Bedrock Edition 26.40" 👁 Image{{upcoming|Chaos Cubed}} outputs [upcoming: Chaos Cubed]), which should also be categorized. 👁 Image