eandr127
- eandr127
- eandr127
- America/New_York
- Yes
- No
Endermen
getangry when hit in creativeWhat I expected to happen was...:
When I hit an enderman in creative it would not get angry.What actually happened was...:
The enderman got angry at me.Steps to reproduce:
1. Find or spawn an enderman.
2. Hit the enderman.
3. Notice how the enderman gets mad at you.
Endermen angry when hit in creative
What I expected to happen was...:
When I hit an enderman in creative it would not get angry.What actually happened was...:
The enderman got angry at me.Steps to reproduce:
1. Find or spawn an enderman.
2. Hit the enderman.
3. Notice how the enderman gets mad at you even though you are in creative.
Endermen get angry when hit in creative
What I expected to happen was...:
When I hit an enderman in creative it would not get angry.What actually happened was...:
The enderman got angry at me.Steps to reproduce:
1. Find or spawn an enderman.
2. Hit the enderman.
3. Notice how the enderman gets mad at you even though you are in creative.
Windows 7 64bit
java version "1.8.0_05"
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)Windows 7 64bit
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Windows 7 64bit
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)Microsoft Windows 7 Professional
6.1.7601 Service Pack 1 Build 7601java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Microsoft Windows 7 Professional 64 bit
6.1.7601 Service Pack 1 Build 7601java version "1.8.0_11" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Pigmen get angry when hit in creative
What I expected to happen was...:
When I hit a pigman in creative it would not get angry.What actually happened was...:
The pigman got angry at me.Steps to reproduce:
1. Spawn a Zombie Pigman.
2. If not already change to survival or adventure mode.
3. Notice how the pigman does not attack you.
4. Switch to creative, and hit the pigman.
5. Switch back to survival or adventure.
6. Notice how the pigman attacks you, even though you were in creative when you hit it..
Windows 7 64bit
java version "1.8.0_05"
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)Windows 7 64bit
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Windows 7 64bit
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)Microsoft Windows 7 Professional
6.1.7601 Service Pack 1 Build 7601java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Microsoft Windows 7 Professional 64 bit
6.1.7601 Service Pack 1 Build 7601java version "1.8.0_11" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Pigmen get angry when hit in creative
What I expected to happen was...:
When I hit a pigman in creative, it would not get angry.What actually happened was...:
The pigman got angry at me.Steps to reproduce:
1. Spawn a Zombie Pigman.
2. If not already, change to survival or adventure mode.
3. Notice how the pigman does not attack you.
4. Switch to creative, and hit the pigman.
5. Switch back to survival or adventure.
6. Notice how the pigman attacks you, even though you were in creative when you hit it.
Microsoft Windows 7 Professional 64 bit
6.1.7601 Service Pack 1 Build 7601java version "1.8.0_
11" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)Microsoft Windows 7 Professional 64 bit
6.1.7601 Service Pack 1 Build 7601java version "1.8.0_20" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Microsoft Windows
7 Professional64 bit
6.1.7601 Service Pack 1Build7601java version "1.8.0_20" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)Microsoft Windows Technical Preview 64 bit
6.4.9841 N/A Build 9841java version "1.8.0_20" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Microsoft Windows Technical Preview 64 bit
6.4.9841 N/A Build 9841java version "1.8.0_2
0" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)Microsoft Windows Technical Preview 64 bit
6.4.9841 N/A Build 9841java version "1.8.0_25" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Microsoft Windows Technical Preview 64 bit
6.4.9841N/A Build 9841java version "1.8.0_25" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)Microsoft Windows Technical Preview 64 bit
6.4.9860 N/A Build 9860java version "1.8.0_25" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Microsoft Windows Technical Preview 64 bit
6.4.9860 N/A Build 9860java version "1.8.0_25" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)Ubuntu 14.04 LTS
java version "1.8.0_25" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Ubuntu 14.04 LTS 64 bit
java version "1.8.0_25" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Ubuntu 14.04 LTS 64 bit
java version "1.8.0_
25" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)Ubuntu 14.04 LTS 64 bit
java version "1.8.0_31" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Ubuntu 14.04 LTS 64 bit
java version "1.8.0_31" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)System Independent
Player unable to turn when at Y: Infinity
What I expected to happen was...:
When I got to Y: Infinity, that I would be able to turn just like any other height.What actually happened was...:
I was unable to turn..Steps to reproduce:
1. Perform command "/tp [playername] ~ ~1.0E308 ~" twice
2. Make sure the Y coordinate is equal to "Infinity"
3. Try to turn, and notice how it is not possible
Microsoft Windows Technical Preview 64 bit
6.4.9841 N/A Build 9841java version "1.8.0_
25" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)Ubuntu 14.04 LTS 64 bit
java version "1.8.0_31" 64 bit
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)




@Galaxy_2Alex, shouldn't you only need to assign 2 GB of ram? http://minecraft.gamepedia.com/14w30a#Changes
I would say that it is more related to
MC-55419than a duplicate of it, as the other bug is focusing on player coordinates and sky effects rather than player rotation.I would agree with that. It should at least stop you from teleporting to a Y position equal to infinity.
Yes, it is fixed now.
It seems that the behaviour was reverted in 1.16-pre3, so this ticket should be reopened.