[MC-1311] When you enter the Nether, the game auto-selects the first item on the toolbar Created: 30/Oct/12 Updated: 02/May/15 Resolved: 06/Dec/12 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Minecraft 1.4.2, Minecraft 1.4.5 |
| Fix Version/s: | Snapshot 12w49a |
| Type: | Bug | ||
| Reporter: | Sid Ben | Assignee: | [Mojang] Nathan Adams |
| Resolution: | Fixed | Votes: | 20 |
| Labels: | None | ||
| Environment: |
Windows 7 64 bit |
||
| Issue Links: |
|
||||||||||||||||||||
| CHK: | |||||||||||||||||||||
| Confirmation Status: | Confirmed | ||||||||||||||||||||
| Description |
|
As the title explains. 1. On the overworld, select the fifth (or any other, except first) item on your toolbar; |
| Comments |
| Comment by Sid Ben [ 07/Dec/12 ] |
|
Sir, you just earned a free hug. |
| Comment by Robin Bastiaan [ 06/Dec/12 ] |
|
Awsome! Thank you alot! |
| Comment by [Mojang] Nathan Adams [ 06/Dec/12 ] |
|
Comes with the added benefit of keeping your selected item per logout/login! |
| Comment by Tails [ 01/Dec/12 ] |
|
Confirmed in 1.4.5 and also applies to end portals, respawning or reloading the world. |
| Comment by Tom Mate [ 21/Nov/12 ] |
|
confirm. quite annoying |
| Comment by Robin Bastiaan [ 02/Nov/12 ] |
|
Confirmed! This bug occurs in survival and in creative when traveling between worlds (doesn't matter which one) |
| Comment by Meta [ 31/Oct/12 ] |
|
Yeah, very annoying, too |
| Comment by Rolf Redford [ 31/Oct/12 ] |
|
Yeah this is why I always put sword on slot #1. Usually, you do not suddenly need to eat or build after entering world, but defense you do need. |
| Comment by [Mod] Ezekiel (ezfe) [ 30/Oct/12 ] |
|
This is not specifically going to the nether, its loading the world. The client forgets what slot its in when it leaves the world, and the server sends the client the player profile, but does not store the current slot in the inventory you are using. |
| Comment by DetachableMonkey (Kurt Boyer) [ 30/Oct/12 ] |
|
I can confirm this issue with 1.4.2. It has been around for quite a few versions. |