Minecraft 1.3 Update - What's New
Merged singleplayer and multiplayer code into one unified codebase. Added emeralds, trading with villagers, temples, and adventure mode.
Overview
Minecraft 1.3 is a stable release for Minecraft: Java Edition, published on August 1, 2012. It is the base 1.3 release, known to the community as Adventure Update Part II, and it bundles 13 documented changes across 3 areas of the game.
The work in this update spans gameplay, blocks & items, and commands. On the gameplay side it brings Singleplayer now runs an integrated server and Adventure mode for custom maps.
Within Minecraft's history, 1.3 is the release that unified singleplayer onto an internal server and added trading. Its signature additions include emerald trading, tripwire hooks, and the Ender Chest, and this release is where they first arrived for everyone playing on the stable channel.
Changes
#Gameplay(6)
- Singleplayer now runs an integrated server
- Added Adventure mode for custom maps
- Added trading with villagers using emeralds
- Added desert temples and jungle temples
- Added bonus chest option for new worlds
- Added LAN multiplayer support from singleplayer
#Blocks & Items(5)
- Added emerald ore and emerald block
- Added Ender Chest
- Added tripwire hook and tripwire
- Added written books (Book and Quill)
- Added cocoa beans as plantable crop
#Commands(2)
- Added /seed command
- Added /gamerule command
Server Admin Migration Guide
- Significant internal changes - update server jar carefully
- Single and multiplayer code merged - performance characteristics may differ
- Test plugin compatibility before deploying
Known Issues
- Performance regression due to integrated server in singleplayer
- Some redstone behavior changed slightly
What This Means
For players
If you play singleplayer or on a server, 1.3 is safe to update to. New blocks and items become craftable, and existing worlds carry forward without resetting. Back up your save first as a habit, then load it on the new version.
For server admins
Server owners should not rush a production upgrade. Wait for your platform (Paper, Spigot, Fabric, Forge, NeoForge) and every plugin or mod to publish 1.3-compatible builds, then test the full stack on a staging copy before touching the live world. Command or datapack changes in this version can break custom map logic, so re-check those especially.
Background & Context
- 1.3 (Adventure Update Part II) was a major version bump, the kind of release that introduces a new theme of content to the early 1.x era.
- Minecraft: Java Edition keeps full backward compatibility for worlds, so saves created on 1.3 continue to open and upgrade on later releases.
- Always keep a backup of important worlds before changing versions; the Astroworld versions database tracks client and server compatibility for 1.3.
Frequently Asked Questions
When was Minecraft 1.3 released?
Minecraft 1.3 was released on August 1, 2012 as a stable release for Minecraft: Java Edition.
What does the Minecraft 1.3 update add?
Merged singleplayer and multiplayer code into one unified codebase. Added emeralds, trading with villagers, temples, and adventure mode. Notable entries include: Singleplayer now runs an integrated server; Added Adventure mode for custom maps; Added trading with villagers using emeralds. In total it documents 13 changes across 3 categories.
Is Minecraft 1.3 stable for survival worlds?
Yes. 1.3 is a stable release; existing worlds upgrade in place and the version is intended for normal singleplayer and multiplayer play. Back up your save before updating as a precaution.
Can I run 1.3 on a Minecraft server?
You can, but wait until your server software (such as Paper, Spigot, Fabric, Forge, or NeoForge) and all of your plugins or mods publish builds compatible with 1.3, then test on a staging server before upgrading the live one.
What is Minecraft 1.3 called?
Minecraft 1.3 is Adventure Update Part II. It is the release that unified singleplayer onto an internal server and added trading, headlined by emerald trading, tripwire hooks, and the Ender Chest.
Are there known issues in 1.3?
Yes. Documented issues for this build include: Performance regression due to integrated server in singleplayer; Some redstone behavior changed slightly. These are typically resolved in a later point release.
Looking for version compatibility info?
Check client and server version details on our versions database.