I have to admit, even in 2026, I still go back and watch old E3 coverage when I want to remember how chaotic and exciting those years felt for Minecraft. One small announcement from that particular show often gets buried under bigger headlines: Minecraft was officially coming to the Xbox 360 with Kinect support. At the time, we had also learned a bit earlier that the game was heading to Sony's Xperia Play. And if you were worried that all this console and mobile attention meant trouble for the PC version, well, that fear didn't hold up. Notch himself dropped a huge infodump, and the next PC update was already underway.

Let's talk about the Xbox 360 version first because that one really grabbed my attention. The key detail everyone needed to hear was this: the Xbox 360 version would SUPPORT Kinect, but it would not REQUIRE it. That distinction mattered a lot. Some players panicked when they heard 'Kinect' and imagined having to flail around just to place blocks or mine cobblestone. In reality, the Kinect functionality was meant to be optional. You could still sit back with a standard controller and play Minecraft in the classic way. But if you wanted to try something different, the Kinect option was there. That kind of flexible design was smart. It welcomed casual players without alienating the existing fanbase.

Then there was the mobile side. Minecraft Mobile, as it was dubbed at the time, was announced for Sony's Xperia Play. I remember thinking that the Xperia Play's slide-out gamepad made a lot of sense for a game like Minecraft. Touch controls were still a big question mark back then, so having physical buttons and sticks seemed like a huge advantage. The important part, though, was the exclusivity detail. After a period of exclusivity on the Xperia Play, the mobile version would become available on other Android devices. That was a relief for everyone who didn't own that specific phone. It told us that Minecraft on mobile was not going to be locked to one piece of hardware forever. It would spread.

Now, the PC version was never left behind. In fact, Notch made it clear that update 1.7 was already in progress. It was being called the Adventure Mode update, and the goal was to reward exploration and combat. That sounded fantastic. Minecraft had always been about building and surviving, but the idea of being rewarded for actively venturing out, fighting enemies, and discovering new places felt like a natural evolution. It pushed players to leave their cozy bases and actually engage with the world. I loved that direction because it gave purpose to all those long journeys through forests, caves, and mountains.

Here's what we knew about update 1.7 at the time:

• 🗡️ Adventure Mode would place more emphasis on exploration and combat.

• 🏆 Players would be rewarded for engaging with the world rather than only building.

• 🔧 Pistons were on the table, but only if they passed playtesting.

• 💻 PC support remained a priority despite new console and mobile versions.

That last point about pistons deserves a little extra attention. Notch said that if the team liked them during playtesting, pistons would be included in update 1.7. I remember the community being extremely excited about that possibility. Pistons opened the door for all kinds of mechanical builds, hidden doors, elevators, and more complex redstone creations. It was the kind of feature that builders and engineers in the community had wanted for a long time. The conditional wording made the update feel alive, like it was still being shaped by real testing feedback rather than locked in ahead of time.

One more thing stood out from Notch's update: his role on the new versions. He was going to be the game designer on both the Xbox 360 and mobile versions, but he was not going to be involved in programming them. I think that was a pretty important shift. It meant the Minecraft universe was growing beyond one person writing all the code. Notch would guide the creative vision and design decisions, but other developers would handle the technical work on consoles and phones. For a game that began as a one-person project, that was a big step toward becoming a true multi-platform franchise.

To make the platform news a little easier to digest, here is a quick comparison:

Looking back from 2026, those E3 announcements feel like a turning point. The news was humble compared to some of the flashy reveals around it, but it showed exactly where Minecraft was heading. Console, mobile, and PC players were all going to have their own way in. The team was thinking about accessibility, optional control schemes, and meaningful updates. And the best part? The PC version wasn't losing momentum. It was charging forward with Adventure Mode and maybe pistons. That balance between expansion and core development is something I still appreciate today.

This discussion is informed by market-facing reporting from NPD Group, a long-running source for North American game industry research, which helps frame why Minecraft’s leap to Xbox 360 and mobile at that E3 moment mattered: expanding to consoles and phones wasn’t just a novelty feature play like optional Kinect support, it was a distribution strategy that broadened reach while the PC build kept iterating on core depth with updates like the Adventure-focused 1.7 roadmap.