Talk:Chase the Skies

please see reference [1] of this page:

1 - File names of the images in a Minecraft.net article contains "SummerDrop". Examples include MCV_SummerDrop_Editorial_Exclusive_DotNet_Blog_Editorial_1170x500.jpg.

furthermore, the schedule for drops has already been shown to be seasonal, so it's pretty safe to assume that the "next game drop" is a summer drop. if you really think otherwise i think you shouldn't leave us blank on the "why" of your feedback
mariberry-hearn! (talk) 02:59, 18 March 2025 (UTC)

No, I think that yes, there will be a summer drop, it's just not going to be bedrock 1.21.80 & add the player locator bar. I think it will probably be anunced completely at Minecraft Live. 169.204.203.208 15:28, 18 March 2025 (UTC)

It might add the Player Locator Bar, just it won't be 1.21.80 (probobly) 169.204.203.208 15:30, 18 March 2025 (UTC)

do you have any actual evidence to present besides "i think that [x]" and a probably? because the contents of the player locator bar announcements very much lead to the assumption that the player locator bar is for the next game drop that would be released at summer - again, please see reference 1 of this page
mariberry-hearn! (talk) 16:29, 18 March 2025 (UTC)

The player locator is experimental, so it will probobly be in the next drop, but not 1.21.80 witch (looking at what their history) will just be mostly bug fixes. I guess it doesn't mater untill minecraft live though, when we'll see what it actualy is. – Unsigned comment added by Simbainspace (talk • contribs) at 03:02, 19 March 2025 (UTC). Please sign comments with ~~~~

Thank you (or whoever did it) for adding (assumed) for 1.21.80. – Unsigned comment added by Simbainspace (talk • contribs) at 23:39, 23 March 2025 (UTC). Please sign comments with ~~~~

In the article: "Now that all the features from our first game drop of 2025 are in testing, we thought why not start on our next game drop?"

So it's clear that player locator bar is the content of next drop. -- Leo768 (talk) 16:33, 18 March 2025 (UTC)

At the moment, there are 2 version pages (Java Edition 1.21.6 and Bedrock Edition 1.21.80) which are (as this article states) assumed to be the release of the Summer Drop.
First, I 👁 Image
 Disagree that BE 1.21.80 will be the release of the Summer Drop, because the Locator Bar was confirmed to be added in the drop, but in 1.21.80 dev versions, it's locked behind an experiment. This means that 1.21.80 will likely not be the full release, but a smaller update (exactly the same as 1.21.60, which also had some experimental features from Spring to Life).
Dev versions for the 'full release' of the Summer Drop have not yet been released, but I think we can assume that it will be JE 1.21.6 and BE 1.21.90. However, this wiki is not for assumptions, so I suggest to remove Java Edition 1.21.6, along with all indications that BE 1.21.80 will be the full release of the Summer Drop, and leave all information about the Summer Drop on this page.
1.21.80 and 1.21.6 should only contain information about features that have already been added to dev versions. As soon as the first snapshot for 1.21.6 is released, that page can be re-created with only the features from the snapshot.
If we want to keep assumed version pages, Bedrock Edition 1.21.90 should contain the same information as 1.21.6, but I'm no fan of this. MinecraftBedrockPlayer7 (talk)(contribs) 👁 Image
09:26, 25 March 2025 (UTC)

If anyone has sources that 1.21.6 will be the release of the Summer Drop, that page can be kept. MinecraftBedrockPlayer7 (talk)(contribs) 👁 Image
09:35, 25 March 2025 (UTC)

I agree strongly, I said the SAME THING above. – Unsigned comment added by Simbainspace (talk • contribs) at 00:47, 27 March 2025‎ (UTC). Please sign comments with ~~~~

Support deleting Java Edition 1.21.6 - this wiki is not a crystal ball. Arina (she/her) 10:14, 25 March 2025 (UTC)

👁 Image
 Strong oppose deleting these pages.

• We did the same thing for 1.21.5 when its name was not yet confirmed.
• We know that some version containing these features will be released, the only thing we don't know is what the version name will be.
• The "Conjecture" box at the top of the article clarifies that the exact version name of this version is not yet confirmed.
• In addition to summarizing content for the next drop, they also serve as collecting features from dev versions.
• Also we know by analytics that these pages are extremely popular with readers. I cannot overstate that.

| violine1101 ^(talk) 16:15, 25 March 2025 (UTC)

we know by analytics that these pages are extremely popular with readers - what analytics? Could you elaborate? Arina (she/her) 20:48, 26 March 2025 (UTC)

Admins have access to analytics of how many page views each article gets. Articles for future Java Edition releases are consistently among the top 20 pages across the entire wiki, if not higher. | violine1101 ^(talk) 15:45, 30 March 2025 (UTC)

I've now rewritten the introduction to Java Edition 1.21.6 to make the current state of affairs clearer. | violine1101 ^(talk) 15:44, 30 March 2025 (UTC)

We only did the same for 1.21.5 because it had implicit officiality in the form of Slicedlime titles etc. 1.21.6 has nothing yet.  Nixinova   T   C   11:28, 3 April 2025 (UTC)

👁 Image
 Support– notable features for the next drop are already explained on the Summer Drop 2025 article. The version for the game drop has not been confirmed yet, so the version name is just pure speculation. JE 1.21.6 could also easily end up being a hotfix (mentioned by Nixinova on related Talk:Java Edition 1.21.6). And, if these pages are popular, we can merge and redirect to that article instead, effectively removing duplicate information. JE 1.21.6 is already mentioned to be assumed version of the drop in the article, so no need to make a separate article for them. Outrowed (talk) 03:45, 26 March 2025 (UTC) (Last edited on 00:14, 27 March 2025 (UTC))

Guys what about 1.22? Will it be an update or a game drop? Shouldn't the summer drop be 1.22? (Sul4ur) 20:47, 26 March 2025 (UTC)

Perhaps it could be a redirect to "Summer Drop 2025?" ZaLink700 (talk) 01:41, 30 March 2025 (UTC)

I’d say we wait for about a week for a possible snapshot for the Summer Drop.

Anyway, 👁 Image
 Oppose per Violine.

Another question, why are we even discussing the deletion of JE 1.21.6 on a page which isn’t JE 1.21.6? — 3A |  T  C  02:55, 30 March 2025 (UTC)

This is discussed here because it also applies to BE 1.21.80 (sort of). Although that page no longer lists the features announced in Minecraft LIVE (happy ghast), 1.21.80 is still referred to as the release of the Summer Drop, which is in my eyes not true. MinecraftBedrockPlayer7 (talk)(contribs) 👁 Image
08:42, 30 March 2025 (UTC)

We actually don't know if it will be the release. It could be that the locator bar will be moved out of the experiment for 1.21.80, but it could also end up as a minor update like 1.21.60. MinecraftBedrockPlayer7 (talk)(contribs) 👁 Image
08:44, 30 March 2025 (UTC)

It's like when we assumed 1.21.60 was the spring drop and we found out we wasn't. We can just change it based on any newest information. — 3A |  T  C  09:36, 30 March 2025 (UTC)

I have a strong feeling that the summer drop is going to be 1.22.

I mean the locator bar in Bedrock Edition 1.21.80 is an experimental feature, so 1.21.80 is just going to be a minor update.

And also it's been a year since 1.21, so it has to be 1.22. 👁 Image
Sul4ur 11:25, 30 March 2025 (UTC)

I'd also like the summer drop to be 1.22, but as it's a "drop" and all drops so far have been minor updates, it's versioned 1.21.6 for now. Once again, we can just move the page. — 3A |  T  C  12:58, 30 March 2025 (UTC)

The article, in its current form, is purely speculative (MCW:RULES#4). It is misleading the readers into thinking JE 1.21.6 is the actual release for Summer Drop 2025, when in reality, there is no snapshot, patch notes, announcement, or any official sources to back that up. Things like this we should act now rather than waiting when it happens. Outrowed (talk) 12:57, 30 March 2025 (UTC)

"The Java Edition version number of this drop has not yet been announced, but is assumed to be 1.21.6."

In addition, the page for JE 1.21.6 does not mention the version number at all; it only mentions it is the release of the summer drop:

"The release of the Summer Drop 2025 is an upcoming version of Java Edition that is set to release in June 2025."

The conjecture tag is also at the very top of the page, showing that the version number is given by the community, and has not been announced yet. We did the same for 1.21.5: We didn't have the version number. Even though there was a snapshot already (25w02a), that still wasn't a "source" to back up the fact that it was 1.21.5. We still treated it as 1.21.5 even if the version number wouldn't be revealed until pre1. During that time, we were also speculating that the version would be a spring drop. At that time, it could very well be just a version like 1.20.2. If we did the same for 1.21.5, I see no reason why we shouldn't do that for 1.21.6.

If we happened to remove this page after any reason, I think we should just move it somewhere else (e.g. a user page) until the first snapshot for .6 is released. It doesn't feel right to just outright delete everything, with this article being reusable. — 3A |  T  C  13:06, 30 March 2025 (UTC)

In addition, the page for JE 1.21.6 does not mention the version number at all; it only mentions it is the release of the summer drop ... – then the title is problematic, it should provide a sufficient description of what is in the article, rather than being the opposite. I should also mention that the quote you referred to before does not exist in the page, the introduction states "The release of the Summer Drop 2025 is an upcoming version of Java Edition that is set to release in June 2025.", which implies that JE 1.21.6 is the release of Summer Drop 2025.

---

The conjecture tag is also at the very top of the page, showing that the version number is given by the community, and has not been announced yet. – the conjecture tag is often used for the topic that is commonly named/referred to by the community, but as it currently shows, there is uncertainty among editors in this discussion whether JE 1.21.6 should be the release version for Summer Drop 2025. I also feel like the tag is being used over the top here. In my experience, conjecture tag is often used for a feature or topic that has definitely exists in the game or at least supported by official sources, things like Expect the unexpected, Monster infighting, etc. As for Legacy Console Edition, Early & Late Classics, they require proper discussion and community consensus before hand on what to name things unofficially.

---

We did the same for 1.21.5: We didn't have the version number. Even though there was a snapshot already (25w02a), that still wasn't a "source" to back up the fact that it was 1.21.5. We still treated it as 1.21.5 even if the version number wouldn't be revealed until pre1. During that time, we were also speculating that the version would be a spring drop. At that time, it could very well be just a version like 1.20.2. If we did the same for 1.21.5, I see no reason why we shouldn't do that for 1.21.6. – there is a reason why we shouldn't speculate, the readers expect this wiki to give factual and reliable information over things that are uncertain and prone to mistake. Many well-known community members refer 25w02a as the first snapshot for the next game drop when it was released ([1], [2]), other speculate whether it was 1.22 or 1.21.5.

---

If we happened to remove this page after a consensus was reached, I think we should just move it somewhere else (e.g. a user page) until the first snapshot for .6 is released. It doesn't feel right to just outright delete everything, with this article being reusable. – I was thinking of merging the article to Summer Drop 2025, where the information there are definite. But if we are trying to preserve the page, then I suggest renaming the title to something else. Outrowed (talk) 14:13, 30 March 2025 (UTC)

I do agree with this, if the pages are decided to be removed they should be preserved somewhere. FireDragons52 06:42, 1 April 2025 (UTC)

I agree that we can assume that 1.21.6 will be the release of the summer drop, but I think such a version page should only list features that have already been added in development versions, like the page 1.21.80 now. MinecraftBedrockPlayer7 (talk)(contribs) 👁 Image
13:50, 30 March 2025 (UTC)

👁 Image
 Very strong support. Despite, summer drop could be for 1.22, despite being a drop. It's been a year since 1.21، so it could be 1.22.

👁 Image
Sul4ur 17:50, 31 March 2025 (UTC)

👁 Image
 Strong support. While the pages are useful, particularly for search results, they don't feel necessary in most ways. Bedrock Edition 1.21.80 is fine, the Summer Drop content is listed under experimental, but I believe it would work instead to have Java Edition 1.21.6 and Bedrock Edition 1.21.90 redirect to this page rather than have version pages. Once snapshots or previews for the Summer Drop itself begin to be released, pages being created makes sense, but as of now they just don't feel necessary. I also disagree that 1.21.6/1.21.90 will be the Summer Drop, I believe they'll be 1.22 due to the June release, but that's getting into more theoretical discussion than discussion related to the Summer Drop version pages. FireDragons52 06:38, 1 April 2025 (UTC)

👁 Image
 Delete 1.21.6. Not official or assumable in any form yet.  Nixinova   T   C   11:29, 3 April 2025 (UTC)

👁 Image
 Strong support. I think Bedrock Edition 1.21.80 should be kept, though not as the release target of the Summer Drop, and Java Edition 1.21.6 should be removed or at least put as a redirect to this page until next Tuesday when an actual snapshot for the upcoming Java Edition release comes out. Sightnado (talk) 19:14, 3 April 2025 (UTC)

then the title is problematic, it should provide a sufficient description of what is in the article, rather than being the opposite.

Is changing the article title to something along the lines of Untitled Java Edition Summer Drop release a viable option? UltraUsurper (talk) 05:40, 5 April 2025 (UTC)

Do note that I was responding to the original quote from user 3A, which might already been resolved by violine on an edit and comment. I do still think naming it "Java Edition 1.21.6" is misleading to readers when there is no version exist for it or official source to confirm, so I recommend renaming to "Upcoming Java Edition version". Plus, in the future, if there are two hypothetical independent announced versions, we could disambiguate to "Upcoming Java Edition version (Summer Drop 2025)" and "Upcoming Java Edition version (XXX Drop)". Note "Upcoming" because it is already confirmed that a snapshot is expected for Summer Drop 2025.^[1] Outrowed (talk) 13:22, 8 April 2025 (UTC)

👁 Image
 Note - If a snapshot for 1.21.6 releases today (which is extremely likely), the discussion about the deletion of the 1.21.6 page will immediately become irrelevant, and we'll only have to talk about 1.21.80's problem. — 3A |  T  C  14:02, 8 April 2025 (UTC)

Not necessarily. This discussion can set a precedent for future versions. Outrowed (talk) 14:03, 8 April 2025 (UTC)

Yep. Anyway, 25w15a just released, we can continue on with the problem with 1.21.80. — 3A |  T  C  14:04, 8 April 2025 (UTC)

AFAIK they still haven't called it 1.21.6 yet; it was announced as "first snapshot of the second game drop of 2025". We still don't know the version number, so "Upcoming Java Edition version" as suggested by Outrowed might still be a more appropriate title, until we have official confirmation. The version certainly needs a page now, now that we have a snapshot for it, so deletion should be off the table. UltraUsurper (talk) 14:42, 8 April 2025 (UTC)

See how we did it for 1.21.5: First snapshot released, page was already called 1.21.5. We’ll probably still look at Slicedlime’s playlist, even if its his personal project.

I will admit, I did create the 1.21.6 page a bit early. I was trying to get the page created as early as possible. — 3A |  T  C  14:58, 8 April 2025 (UTC)

We still don't know for sure that 1.21.6 is going to be the release of the Summer Drop. We don't know that until and unless Mojang explicitly says so in an official context. It could end up being a minor update like 1.21.80 is likely to be, or we might even skip to 1.22. Since we don't have a wiki policy or consensus regarding this, it doesn't matter much what we did for 1.21.5. We shouldn't use unofficial version numbers when we're not sure; "Java Edition Summer Drop release" or "Upcoming Java Edition version" perfectly suffice as placeholder titles. UltraUsurper (talk) 15:25, 8 April 2025 (UTC)

We also didn't know if 1.21.5 was going to be 1.21.5 or 1.22. We did the same thing: use {{conjecture}}, which is made exactly for this situation. | violine1101 ^(talk) 15:28, 8 April 2025 (UTC)

Once again, since there is no clear consensus regarding this yet, as indicated by this discussion, what we did for 1.21.5 isn't super relevant. {{conjecture}} is supposed to be used when something in the game doesn't have an official name or has a common name in the community, not for speculating on future unreleased version numbers (at least not exactly for that purpose). UltraUsurper (talk) 15:44, 8 April 2025 (UTC)

I would argue the usage of {{Conjecture}} in here must at least be supported by community or official sources of naming things. By community, I mean multiple well-known community members providing coverage on the snapshot and referring them as for Java Edition 1.21.6, then it is a topic named by the community. For now, not everyone agreed on calling it 1.21.6, I would at least wait for multiple video covering the new snapshot, Slicedlime is included. Outrowed (talk) 15:55, 8 April 2025 (UTC)

Considering slicedlime's playlist now denotes the version as 1.21.6 and no other major community figures are calling it 1.22, I think it is safe to leave it as 1.21.6. Sightnado (talk) 22:32, 8 April 2025 (UTC)

Yeah, pretty much. Outrowed (talk) 23:55, 8 April 2025 (UTC)

👁 Image
 Comment - With the release of 25w15a, this discussion now feels like it pertains more to precedent rather than these specific version pages. I like the above idea of "Upcoming Java Edition version", with a redirect from 1.21.6 and from 1.22. Similarly, an "Upcoming Bedrock Edition version" page could be useful as it seems 1.21.80 is the update introducing the experimental options for it, similar to 1.21.60. FireDragons52 20:45, 8 April 2025 (UTC)

With the release of 25w15a and Slicedlime using 1.21.6 and no one else using 1.22, I think the problem of what we should do to the 1.21.6 page is over. For future versions, I think we can do the following:

• Page created after first dev version: use version number, confirm via other community figures
• Page created after announcement of drop but before first dev version: use "Upcoming <insert version> <drop> release", change to version number after it has been sorta confirmed, like point above
• Page created before announcement of drop: delete

— 3A |  T  C  23:48, 8 April 2025 (UTC)

👁 Image
 Oppose for the second point. When a drop is announced, the page for that drop is created documenting all the announced features. Creating seperate version JE and BE pages for the drop would be useless since we don't have any released version to document, and ultimately, we would end up writing the same announced features, i.e. duplicating information from the drop page. Not to mention it could also fall in speculation category, being it too early without any strong evidence to prove. 👁 Image
 Suggestion redirect all pages that are likely going to be searched for the next versions to the existing drop pages, e.g. "Java Edition 1.21.7" and "Bedrock Edition 1.21.90" to "XXX Drop". Outrowed (talk) 00:47, 9 April 2025 (UTC)

P.S. by the "drop page", I mean like Summer Drop 2025 and Spring to Life. Since they document announced features, version page creation before the dev version would be unnecessary, as per my reasoning above. I do support the first and third points, and I'm also going to remove the {{Move}} template on Java Edition 1.21.6 now since there are now strong community/semi-official evidence in favor of JE 1.21.6. Outrowed (talk) 16:07, 9 April 2025 (UTC)

👁 Image
 Comment - I think redirects are also important, e.g. if another drop is announced before 1.22 releases, we'd have redirects to the appropriate Summer Drop version pages from 1.21.7, Java Edition 1.21.7, Java Edition 1.22 (Java), 1.21.90, Bedrock Edition 1.21.90, and Bedrock Edition 1.22.0 (Bedrock). FireDragons52 11:17, 10 April 2025 (UTC)

I think these titles should redirect to Summer Drop 2025 because these updates could (and will likely be) a different update (read: game drop) than 1.21.6 and 1.21.80. MinecraftBedrockPlayer7 (talk)(contribs) 👁 Image
12:38, 10 April 2025 (UTC)

Just look at what happens when Mojang doesn't say two versions...

👁 Image
Sul4ur 04:14, 11 April 2025 (UTC)

Will the Summer Drop 2025 have one or more new Hostile Mob(s)? Zachaybarb (talk) 18:31, 9 April 2025 (UTC)

Everything we know about the Summer Drop for now is included in the article. We don't know if there will be. MinecraftBedrockPlayer7 (talk)(contribs) 👁 Image
19:08, 9 April 2025 (UTC)

i agree dude 2601:1C0:5900:4060:1046:232B:B629:1CEE 13:50, 23 April 2025 (UTC)

Can you provide specific information about what is not consistent with other drop pages? MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
09:50, 16 May 2025 (UTC)

Spring to Life Page for example matches The Garden Awakens style in terms of the way it was organized. I remember trying to make things consistent though. Jaime-Spec MC (talk) 08:03, 18 May 2025 (UTC)

This is no longer a upcoming game drop 169.0.218.175 16:01, 1 June 2025 (UTC)

It's not out yet.  Nixinova   T   C   08:15, 2 June 2025 (UTC)

It's out now! 169.1.122.66 09:54, 21 June 2025 (UTC)

It was not. BDJP ^(t|c) 09:47, 2 June 2025 (UTC)

It was added in 25w15a on Java. It was added in The Garden Awakens drop only on Bedrock LiteraGame (talk) 10:19, 2 June 2025 (UTC)

For example, Spring to Life uses the banner File:Warm leash.jpeg from https://www.minecraft.net/content/dam/minecraftnet/games/minecraft/screenshots/mc-live2025-springtolife.jpg.

I'd like to suggest File:Happy Ghast in Canyon.png from Minecraft LIVE - March 2025. But there are lots of other good images out there. --Simanelix ^(T|C) 20:28, 3 June 2025 (UTC)

In my opinion File:Trio of happy ghasts.webp from the Our next game drop has a name article on Minecraft.net. Maybe it isn't very suitable because of the Vibrant Visuals that won't be available on Java Edition, but it also shows the new leashing mechanics, a big part of this update. LiteraGame (talk) 00:41, 4 June 2025 (UTC)

Previous infoboxes before Spring to Life have separate JE and BE banners, don't know why STL doesn't have one. We could have Vibrant Visuals for BE, and normal graphics for JE. Outrowed (talk) 01:08, 4 June 2025 (UTC)

P.S. This would be good candidate File:SummerDrop Leash A.jpeg for JE banner. Outrowed (talk) 01:15, 4 June 2025 (UTC)

I agree! It shows both the leashes being used and happy ghasts, both which are kinda the main focus of CTS. Can we add it to the page now or should we wait a bit more? LiteraGame (talk) 01:23, 4 June 2025 (UTC)

We should wait. I think? Idk. We don't need to rush too much is what I mean. --Simanelix ^(T|C) 02:38, 4 June 2025 (UTC)

Separate boxes would be good here, especially for showing vibrant visuals vs no vibrant visuals. Vibrant visuals is a pretty big feature imo. --Simanelix ^(T|C) 02:40, 4 June 2025 (UTC)

Yeah, kind of like the Mushroom Fields page. But I don't think it would be fitting for an update, since normally both images are in the same box. LiteraGame (talk) 03:15, 4 June 2025 (UTC)

That would be cool! --Simanelix ^(T|C) 03:17, 4 June 2025 (UTC)

I created a test page showing both infobox options to visualize it a bit better: User:LiteraGame/Test_CTS LiteraGame (talk) 13:16, 4 June 2025 (UTC)

I don't like the idea of splitting the infobox image into a Java and Bedrock image, I think just one image (with Vibrant Visuals) is better. This is not about showcasing a feature like the biome infoboxes, it's just an overview of the additions in this update, and Vibrant Visuals is one of the main additions despite being Bedrock only. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
13:19, 4 June 2025 (UTC)

We're thinking about adding two images because it was the pattern before Spring to Life. Tricky Trials, The Garden Awakens and other previous updates had two images, each from one edition. We're just thinking about how to implement it on the CTS page. LiteraGame (talk) 13:45, 4 June 2025 (UTC)

I don't see 2 images in Spring to Life. But I 👁 Image
 Support the 2nd proposal on your test page, for consistency with other articles. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
13:51, 4 June 2025 (UTC)

Yeah. Stacked images look better to me. --Simanelix ^(T|C) 16:51, 4 June 2025 (UTC)

Showing the locator bar to some degree would also be a good idea. Though obviously these banners are made with the GUI off. Also, I think the locator bar is not really important enough to include in the banner. But it's a potential idea. We might also want to take our own screenshot for the banner. Though that would require some extra work and therefore might not be the best idea. --Simanelix ^(T|C) 02:41, 4 June 2025 (UTC)

Just look at the spring to life page

the two are completely different in structure 37.101.241.87 14:01, 24 June 2025 (UTC)

Just noticed the same happens in major versions before 1.19 37.101.241.87 14:05, 24 June 2025 (UTC)

Recently there's been multiple cases of users changing the structure of named update pages without getting any consensus and not going all the way with it sadly. I definitely think the structure used on this page should be standard though. - Harristic / Talk 👁 Image
14:10, 24 June 2025 (UTC)

It should definitely be discussed and standardized. If every editor does things their own way, all these pages turn into a mess.--Capopanzo (talk | contribs) 14:21, 24 June 2025 (UTC)

Since Bedrock is 1.21.90 will major update 1.22 be in the works? Zachaybarb (talk) 18:49, 27 June 2025 (UTC)

1.21.100 is already in development, so probably not for a while. == Rout | Talk 20:34, 27 June 2025 (UTC)

I think we should include both the Dennis painting and the Lava Chicken disc to this page, as both were added in hotfixes to the main version and wouldn't belong to any other named update otherwise. | violine1101 ^(talk) 19:10, 4 July 2025 (UTC)

👁 Image
 Weak support. I think they're sort of a part of the Chase the Skies update, they're some kind of last-minute addition that just missed the update. If we do list it here, we should also include it in the navbox as well as the versions that added these (1.21.93 and 1.21.7). These versions should also be added in the infobox and a short explanation should be added in the intro. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
19:16, 4 July 2025 (UTC)

👁 Image
 Support - 1.21.7 still falls under the banner of Chase the Skies. == Rout | Talk 19:16, 4 July 2025 (UTC)

I think Nether Update handled this issue well. == Rout | Talk 19:17, 4 July 2025 (UTC)

👁 Image
 Support   — 👁 Image
^{(Talk | Contributions | pt)} 20:16, 4 July 2025 (UTC)

👁 Image
 Done | violine1101 ^(talk) 22:01, 26 July 2025 (UTC)

Shouldn't the Happy Ghast Pilot Coat be mentioned in the promotion section? All of the other character creator stuff is already mentioned. D62 21:45, 21 December 2025 (UTC)

So you haven’t fixed the regular ghast icon, and the icon in the wiki for Chase the Skies is a FAN-MADE PICTURE OF A HAPPY GHAST! Please update the texture for it and use it as the icon. You did it with the zombie horse-so do it for the ghast. Sorry if I sounded rude. GoIden Dandelion (talk) 14:55, 7 June 2026 (UTC)

Some creative liberties have to be taken when downscaling a 32x32 texture to 16x16 for use with EntitySprite. Neither sprite is noticeably incorrect (making the happy ghast icon closer to its actual texture would make it far less recognizable in fact), so I see no reason to change them. 👁 Image
Sightnado ^{t | c} 15:03, 7 June 2026 (UTC)