Minecraft Chase the Skies: Java 1.21.6 & Bedrock 1.21.90 Guide

Chase the Skies arrived on June 17, 2025. The exact final-release boundary used here is Minecraft Java Edition 1.21.6 and Minecraft Bedrock Edition 1.21.90. Mojang Studios is the creator. Check the full number before following a guide, joining a server, or deciding that a feature is missing.

What changes the way a group travels

The official overview describes a progression from dried ghast to ghastling and then happy ghast. A happy ghast can use a dyeable harness for flight. The same drop introduces the Player Locator Bar, which helps show other players in multiplayer; crouching can hide a player from that display. Together, those features turn the update into a coordination problem as much as a collection task.

Before a group starts, choose one objective: raise the creature, learn the flight controls, move supplies, or build at altitude. Trying all four with valuable gear on the first session creates avoidable confusion. Establish a clear launch area, a wide landing area, spare storage on the ground, and an agreed signal for a player who intentionally crouches out of the locator display.

Assign one player to observe from the ground during the first flight. That person can confirm the route, recover dropped supplies, and distinguish a control problem from poor landing visibility.

Exact release tuple

The overview supports both editions, but it does not prove identical controls, render distance, device performance, or Vibrant Visuals availability everywhere. A Java server and a Bedrock client do not become compatible merely because the drop name matches. Use the edition-specific changelog for technical details.

Safe update path

1. Write down the edition and full version for the world owner, server, and every participating client.
2. Stop the world cleanly and make a complete backup outside the active save location.
3. Restore the backup into a disposable test profile or server path. A backup that has never opened is not yet a verified restore.
4. Update the copy to Java 1.21.6 or Bedrock 1.21.90. Keep resource packs and add-ons in their recorded order.
5. Open familiar builds, check player inventories and entities, save, close, and reopen.
6. Run the first happy-ghast and locator-bar session with expendable supplies.
7. Move the primary world only after the owner accepts the test result.

On Realms, consoles, or hosted services, update timing may be controlled by the platform. If the server rejects a connection, compare the displayed edition and full version instead of reinstalling randomly. MineBrush did not test a specific Realm, server host, controller, graphics mode, phone, or third-party pack.

First-session checklist

• Keep the raising process separate from the first flight test so the group knows which step failed.
• Practice boarding, steering, landing, and dismounting without rare inventory.
• Agree whether the locator bar is being used for regrouping or disabled tactically by crouching.
• Do not place the only storage platform where a failed landing can strand the group.
• Verify each player’s controls locally; do not assume keyboard, controller, and touch prompts match.

Troubleshoot and roll back

If a player cannot see expected content, first confirm the edition and exact release. If the locator result differs, check whether the player is crouching before treating it as a bug. If controls, visuals, or performance differ by device, preserve that device’s version and settings in the report. If the copied world stops saving, entities vanish, or a required pack fails, stop the rollout and restore the verified pre-update tuple.

Rollback means restoring the old world together with its old game version, server files, add-ons, resource packs, and permissions. It is not a promise that content saved in a newer release will downgrade safely.