Fenhl (Max Dominik Weber)
- fenhl
- fenhl
- Etc/GMT
- Yes
- No
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
MCL-1533![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
MC-59769![[Mojang] Jeb (Jens Bergensten)](../../../data/assets/gravatar/jeb.jpeg){kind=small}
When trying to type a special character into the in-game chat (or anywhere else), nothing happens.
This bug occurs regardless of the Minecraft version (tested in 1.5.1, 1.5.2pre, 13w16a, and 13w1
8b) when using the new launcher. It does not occur (again, regardless of Minecraft version, tested in 1.5.1 and 1.5.2pre) when using the “official”/old launcher.Examples of affected characters are:
ä (U+E4 LATIN SMALL LETTER A WITH DIAERESIS)
Ü (U+DC LATIN CAPITAL LETTER U WITH DIAERESIS)
ß (U+DF LATIN SMALL LETTER SHARP S)
… (U+2026 HORIZONTAL ELLIPSIS)When trying to type a special character into the in-game chat (or anywhere else), nothing happens.
This bug occurs regardless of the Minecraft version (tested in 1.5.1, 1.5.2pre, 13w16a, 13w18b and 13w21b) when using the new launcher. It does not occur (again, regardless of Minecraft version, tested in 1.5.1 and 1.5.2pre) when using the “official”/old launcher.
Examples of affected characters are:
ä (U+E4 LATIN SMALL LETTER A WITH DIAERESIS)
Ü (U+DC LATIN CAPITAL LETTER U WITH DIAERESIS)
ß (U+DF LATIN SMALL LETTER SHARP S)
… (U+2026 HORIZONTAL ELLIPSIS)The character ` (U+60 GRAVE ACCENT) is not affected, it can be typed as normal even though it is not included in the main “bold” Minecraft font.
When trying to type a special character into the in-game chat (or anywhere else), nothing happens.
This bug occurs regardless of the Minecraft version (tested in 1.5.1, 1.5.2pre, 13w16a, 13w18b and 13w2
1b) when using the new launcher. It does not occur (again, regardless of Minecraft version, tested in 1.5.1 and 1.5.2pre) when using the “official”/old launcher.Examples of affected characters are:
ä (U+E4 LATIN SMALL LETTER A WITH DIAERESIS)
Ü (U+DC LATIN CAPITAL LETTER U WITH DIAERESIS)
ß (U+DF LATIN SMALL LETTER SHARP S)
… (U+2026 HORIZONTAL ELLIPSIS)The character ` (U+60 GRAVE ACCENT) is not affected, it can be typed as normal even though it is not included in the main “bold” Minecraft font.
When trying to type a special character into the in-game chat (or anywhere else), nothing happens.
This bug occurs regardless of the Minecraft version (tested in 1.5.1, 1.5.2pre, 13w16a, 13w18b, 13w21b, and 13w25a) when using the new launcher. It does not occur (again, regardless of Minecraft version, tested in 1.5.1 and 1.5.2pre) when using the “official”/old launcher.
Examples of affected characters are:
- ä (U+E4 LATIN SMALL LETTER A WITH DIAERESIS)
- Ü (U+DC LATIN CAPITAL LETTER U WITH DIAERESIS)
- ß (U+DF LATIN SMALL LETTER SHARP S)
- δ (U+3B4 GREEK SMALL LETTER DELTA)
- … (U+2026 HORIZONTAL ELLIPSIS)
The character ` (U+60 GRAVE ACCENT) is not affected, it can be typed as normal even though it is not included in the main “bold” Minecraft font.
When trying to type a special character into the in-game chat (or anywhere else), nothing happens.
This bug occurs regardless of the Minecraft version (tested in 1.5.1, 1.5.2pre, 13w16a, 13w18b, 13w21b,
and13w25a) when using the new launcher. It does not occur (again, regardless of Minecraft version, tested in 1.5.1 and 1.5.2pre) when using the “official”/old launcher.Examples of affected characters are:
- ä (U+E4 LATIN SMALL LETTER A WITH DIAERESIS)
- Ü (U+DC LATIN CAPITAL LETTER U WITH DIAERESIS)
- ß (U+DF LATIN SMALL LETTER SHARP S)
- δ (U+3B4 GREEK SMALL LETTER DELTA)
- … (U+2026 HORIZONTAL ELLIPSIS)
The character ` (U+60 GRAVE ACCENT) is not affected, it can be typed as normal even though it is not included in the main “bold” Minecraft font.
When trying to type a special character into the in-game chat (or anywhere else), nothing happens.
This bug occurs regardless of the Minecraft version (tested in 1.5.1, 1.5.2pre, 13w16a, 13w18b, 13w21b, 13w25a, and 1.6.1) when using the new launcher. It does not occur (again, regardless of Minecraft version, tested in 1.5.1 and 1.5.2pre) when using the “official”/old launcher.
Examples of affected characters are:
- ä (U+E4 LATIN SMALL LETTER A WITH DIAERESIS)
- Ü (U+DC LATIN CAPITAL LETTER U WITH DIAERESIS)
- ß (U+DF LATIN SMALL LETTER SHARP S)
- δ (U+3B4 GREEK SMALL LETTER DELTA)
- … (U+2026 HORIZONTAL ELLIPSIS)
The character ` (U+60 GRAVE ACCENT) is not affected, it can be typed as normal even though it is not included in the main “bold” Minecraft font.
After switching to a resource pack, launching the game, entering or exiting a world results in a crash.
What I expected to happen was...:
- In case a: The world loads.
- In cases b and c: The main menu loads.
What actually happened was...:
In all three cases: the game crashes with a crash report like that in the attached text file.As a workaround to case c, move or remove the selected resource pack before launching the game. Minecraft will revert to the default pack.
Steps to Reproduce:
- Switch to a resource pack. I used Simplify.
- Note that the game does not crash yet: this is not the same as
MC-17831.- There are at least three ways to reproduce this:
- Case a: Try to enter a singleplayer world or multiplayer server.
- Case b: Try to exit the current world (press "Escape", click "Save and Quit to Title" or "Disconnect").
- Case c: Quit Minecraft and launch it again (click the "Play" button in the MinecraftDev launcher). In this case, the crash occurs after the Mojang logo is displayed.
After switching to a resource pack, launching the game, entering or exiting a world results in a crash.
What I expected to happen was...:
- In case a: The world loads.
- In cases b and c: The main menu loads.
What actually happened was...:
In all three cases: the game crashes with a crash report like that in the attached text file.
Update: The case a crash no longer occurs in Minecraft 1.6.2.As a workaround to case c, move or remove the selected resource pack before launching the game. Minecraft will revert to the default pack.
Steps to Reproduce:
- Switch to a resource pack. I used Simplify.
- Note that the game does not crash yet: this is not the same as
MC-17831.- There are at least three ways to reproduce this:
- Case a: Try to enter a singleplayer world or multiplayer server.
- Case b: Try to exit the current world (press "Escape", click "Save and Quit to Title" or "Disconnect").
- Case c: Quit Minecraft and launch it again (click the "Play" button in the MinecraftDev launcher). In this case, the crash occurs after the Mojang logo is displayed.
After switching to a resource pack, launching the game, entering or exiting a world results in a crash.
What I expected to happen was...:
- In case a: The world loads.
- In cases b and c: The main menu loads.
What actually happened was...:
In all three cases: the game crashes with a crash report like that in the attached text file.
Update: The case a crash no longer occurs in Minecraft 1.6.2.As a workaround to case c, move or remove the selected resource pack before launching the game. Minecraft will revert to the default pack.
Steps to Reproduce:
- Switch to a resource pack.
I usedSimplify.
- Note that the game does not crash yet: this is not the same as
MC-17831.- There are at least three ways to reproduce this:
- Case a: Try to enter a singleplayer world or multiplayer server.
- Case b: Try to exit the current world (press "Escape", click "Save and Quit to Title" or "Disconnect").
- Case c: Quit Minecraft and launch it again (click the "Play" button in the MinecraftDev launcher). In this case, the crash occurs after the Mojang logo is displayed.
After switching to a resource pack, launching the game, entering or exiting a world results in a crash.
What I expected to happen was...:
- In case a: The world loads.
- In cases b and c: The main menu loads.
What actually happened was...:
In all three cases: the game crashes with a crash report like that in the attached text file.
Update: The case a crash no longer occurs in Minecraft 1.6.2.As a workaround to case c, move or remove the selected resource pack before launching the game. Minecraft will revert to the default pack.
Steps to Reproduce:
- Switch to a resource pack.
- There are at least three ways to reproduce this:
- Case a: Try to enter a singleplayer world or multiplayer server.
- Case b: Try to exit the current world (press "Escape", click "Save and Quit to Title" or "Disconnect").
- Case c: Quit Minecraft and launch it again (click the "Play" button in the MinecraftDev launcher). In this case, the crash occurs after the Mojang logo is displayed.
After switching to a resource pack, launching the game, entering or exiting a world results in a crash.
What I expected to happen was...:
- In case a: The world loads.
- In cases b and c: The main menu loads.
What actually happened was...:
In all three cases: the game crashes with a crash report like that in the attached text file.
Update: The case a crash no longer occurs in Minecraft 1.6.2.As a workaround to case c, move or remove
the selected resource packbefore launching the game. Minecraft will revert to the default pack.Steps to Reproduce:
- Switch to a resource pack.
- There are at least three ways to reproduce this:
- Case a: Try to enter a singleplayer world or multiplayer server.
- Case b: Try to exit the current world (press "Escape", click "Save and Quit to Title" or "Disconnect").
- Case c: Quit Minecraft and launch it again (click the "Play" button in the MinecraftDev launcher). In this case, the crash occurs after the Mojang logo is displayed.
After switching to the resource pack Simplify, launching the game, entering or exiting a world results in a crash.
What I expected to happen was...:
- In case a: The world loads.
- In cases b and c: The main menu loads.
What actually happened was...:
In all three cases: the game crashes with a crash report like that in the attached text file.
Update: The case a crash no longer occurs in Minecraft 1.6.2.As a workaround to case c, move or remove Simplify before launching the game. Minecraft will revert to the default pack.
Steps to Reproduce:
- Download Simplify and place it into the .minecraft/resourcepacks folder.
- Note that the zipped version does not appear in the resource packs list.
- Unzip Simplify into the .minecraft/resourcepacks folder.
- Note that it shows up now.
- Switch to Simplify.
- There are at least three ways to reproduce this:
- Case a: Try to enter a singleplayer world or multiplayer server.
- Case b: Try to exit the current world (press "Escape", click "Save and Quit to Title" or "Disconnect").
- Case c: Quit Minecraft and launch it again (click the "Play" button in the MinecraftDev launcher). In this case, the crash occurs after the Mojang logo is displayed.
When attacking a mob (tested with zombies, chickens and endermen) while wearing a Thorns enchanted chestplate, the player is occasionally damaged.
This week's snapshots added support for native fullscreen (using the button in the title bar) on OS X. However, the F11 key (fn F11
on some keyboards) still toggles the old fullscreen feature, which causes weird behavior when used in combination with native fullscreen:Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen. Minecraft is now offset (there is a black border on the top and right side of the screen).
- Deactivate native fullscreen. The game does not adapt to the smaller window size.
An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. (Also it would be nice if
CtrlCmd F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)This week's snapshots added support for native fullscreen (using the button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles the old fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen. Minecraft is now offset (there is a black border on the top and right side of the screen).
- Deactivate native fullscreen. The game does not adapt to the smaller window size.
An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. (Also it would be nice if ctrl cmd F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)
OS X 10.9 or 10.10
This week's snapshots addedsupport for native fullscreen (using the button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still togglesthe oldfullscreen feature, which causes weird behavior when used in combination with native fullscreen:Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen. Minecraft is now offset (there is a black border on the top and right side of the screen).
- Deactivate native fullscreen. The game does not adapt to the smaller window size.
An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. (Also it would be nice if ctrl cmd F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)
Since snapshot 13w47c, Minecraft has support for native fullscreen (using the green button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles Minecraft's own fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it.
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen. Minecraft is now offset (there is a black border on the top and right side of the screen).
- Deactivate native fullscreen. The game does not adapt to the smaller window size.
An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. (Also it would be nice if ctrl cmd F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)
Since snapshot 13w47c, Minecraft has support for native fullscreen (using the green button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles Minecraft's own fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it.
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen. Minecraft is now offset (there is a black border on the top and right side of the screen).
- Deactivate native fullscreen. The game does not adapt to the smaller window size.
An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. (Also it would be nice if ctrl cmd F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)
Since snapshot 13w47c, Minecraft has support for native fullscreen (using the green button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles Minecraft's own fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it.
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen. Minecraft is now offset (there is a black border on the top and right side of the screen).
- Deactivate native fullscreen. The game does not adapt to the smaller window size.
An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. However, this will first require support in LWJGL. (Also it would be nice if ctrl cmd F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)
Since snapshot 13w47c, Minecraft has support for native fullscreen (using the green button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles Minecraft's own fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it.
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen. Minecraft is now offset (there is a black border on the top and right side of the screen).
- Deactivate native fullscreen. The game does not adapt to the smaller window size.
An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. However, this will first require support in LWJGL. (Also it would be nice if
ctrl cmdF would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)Since snapshot 13w47c, Minecraft has support for native fullscreen (using the green button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles Minecraft's own fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it.
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen. Minecraft is now offset (there is a black border on the top and right side of the screen).
- Deactivate native fullscreen. The game does not adapt to the smaller window size.
An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. However, this will first require support in LWJGL. (Also it would be nice if ⌃⌘F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)
OS X 10.9 or 10.1
0OS X 10.9, 10.10, or 10.11
Since snapshot 13w47c, Minecraft has support for native fullscreen (using the green button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles Minecraft's own fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it.
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen. Minecraft is now offset (there is a black border on the top and right side of the screen).
- Deactivate native fullscreen. The game does not adapt to the smaller window size.
An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. However, this will first require support in LWJGL. (Also it would be nice if ⌃⌘F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)
Since snapshot 13w47c, Minecraft has support for native fullscreen (using the green button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles Minecraft's own fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it.
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen.
Minecraft is now offset (there is a black border on the top and right side of the screen).This no longer occurs in OS X 10.11 “El Capitan”.- Deactivate native fullscreen.
The game does not adapt to the smaller window size.This no longer occurs in OS X 10.11 “El Capitan”.An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. However, this will first require support in LWJGL. (Also it would be nice if ⌃⌘F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)
Since snapshot 13w47c, Minecraft has support for native fullscreen (using the green button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles Minecraft's own fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it.
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen.
Minecraft is now offset (there is a black border on the top and right side of the screen).This no longer occurs in OS X 10.11 “El Capitan”.- Deactivate native fullscreen.
The game does not adapt to the smaller window size.This no longer occurs in OS X 10.11 “El Capitan”.An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. However, this will first require
support inLWJGL. (Also it would be nice if ⌃⌘F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)Since snapshot 13w47c, Minecraft has support for native fullscreen (using the green button in the title bar) on OS X. However, the F11 key (or fn F11 depending on keyboard type and a setting in System Preferences) still toggles Minecraft's own fullscreen feature, which causes weird behavior when used in combination with native fullscreen:
Steps to reproduce:
- Launch the game.
- Activate native fullscreen.
- Activate F11 fullscreen. The screen seems to switch to the Desktop space, but then draws fullscreen Minecraft over it.
- Deactivate F11 fullscreen. Minecraft is back to window mode.
- Activate native fullscreen.
Minecraft is now offset (there is a black border on the top and right side of the screen).This no longer occurs in OS X 10.11 “El Capitan”.- Deactivate native fullscreen.
The game does not adapt to the smaller window size.This no longer occurs in OS X 10.11 “El Capitan”.An easy fix for this would be to change the F11 key so that it also toggles native fullscreen on OS X. However, this will first require an update to LWJGL 3. (Also it would be nice if ⌃⌘F would toggle native fullscreen as well, since that's the keyboard shortcut other apps use.)
OS X 10.9, 10.10, or 10.1
1OS X 10.9, 10.10, 10.11, or 10.12
Native fullscreen on OSXand F11 don't mixNative fullscreen on macOS and F11 don't mix
OS
X10.9, 10.10, 10.11, or 10.12macOS 10.9, 10.10, 10.11, or 10.12
Duplicate of
MC-54008.
When the worldborder expands slowly, it is possible to walk onto a block as soon as the border starts expanding into it. However, until the border catches up to your exact position within that block, you will take suffocation damage. This also applies to mobs, like bats flying into the border.
Expected behavior:
- The area that players and mobs can move into is not rounded up to the nearest block.
- Alternatively, the area in which players and mobs do not take suffocation damage is also rounded up to the nearest block.
I originally wrote this as a comment on
MC-54300, because I mistook it for the same issue.Steps to reproduce: (only tested in singleplayer)
- Name a hostile mob.
- Go to spectator mode.
- The mob despawns.
I originally wrote this as a comment on
MC-54300, because I mistook it for the same issue.Steps to reproduce: (only tested in singleplayer)
- Name a
hostile mob.Go to spectator mode.The mob despawns.I originally wrote this as a comment on
MC-54300, because I mistook it for the same issue.Steps to reproduce: (only tested in singleplayer)
- Name a spawn egg.
- Spawn a mob with it.
- Go to spectator mode.
- The mob despawns.
Named mobs despawn when going into spectator modeMobs from named spawn eggs despawn when going into spectator mode
Changing worldborder size is inconsistent / behaves erratically when the border is already moving
There are 2 ways to slowly set the worldborder size: /worldborder set and /worldborder add. These behave inconsistently when applied to already moving worldborders. For example:
- /worldborder set 100
- /worldborder set 10 60
- the border starts moving. type the following after around 10 seconds:
- /worldborder set 20 10
- the border suddenly jumps to a diameter of 10, then expands out to 20
The behavior I expected is that the worldborder changes its speed to shrink from its current size (somewhere around 85 if you indeed waited 10 seconds in step 3), not its old target size (10), to
its new target size (20). But if this isindeedintended behavior, it is inconsistent with the following:
- /worldborder set 1
- /worldborder add 1 60
- the border starts moving. type the following after around 10 seconds:
- /worldborder add 1 10
- the border does not jump to a diameter of 2, but instead adds 1 to its current size (which is around 1.2) and uses that as its new target size
This behavior seems weird, especially considering that /worldborder add was added with the Captive Minecraft map in mind. In Captive Minecraft, you expand the worldborder by getting achievements, 1 meter per achievement. If the map were to be changed to use /worldborder add, and a player were to get 2 achievements in quick succession (as is often the case with Time to Mine! and Getting an Upgrade), the border would not expand the full 2 blocks.
But the first behavior is also problematic, for example when you want to change worldborder size in steps in order to prevent it from getting out of sync with the tick speed (since the rate at which the border moves is independent from tick lag). If the server ticks too fast for some reason, the worldborder will jump forward when it is being resynchronized.
I think the correct behavior would be to always use the current size as the starting size for the new animation (to prevent the jumps described in the first scenario), but to use the old target size as the base for calculating the new target size when using /worldborder add.
height limit decreased by 1Height limit decreased by 1
After connecting to a server, I was after a minute or two disconnected with an io.netty.handler.timeout.ReadTimeoutException.
When I go back to the server list, the server says that 1 player is online. Hovering over the player count, that player is myself.
Attempting to reconnect immediately displays the same ReadTimeoutException. For whatever reason, the server thinks I'm still online and that causes any additional connection attempts to fail.
I tried to kick myself using the server console, which displayed “Kicked Fenhl from the game” but didn't actually cause any changes to the server status.
The bug affects the same Survival server I mentioned in the comments of
MC-61128(after the server restart that fixedMC-61128for me), but not the Creative server, so the two issues might be related. Restarting the server again fixes this but causesMC-61128to occur again.
The server crashes randomly. Most recent crash report attached.
Description: Watching Server java.lang.Error at java.util.ArrayList.indexOf(ArrayList.java:298) at java.util.ArrayList.contains(ArrayList.java:281) at java.util.ArrayList.batchRemove(ArrayList.java:700) at java.util.ArrayList.removeAll(ArrayList.java:671) at aqa.i(SourceFile:1339) at ql.i(SourceFile:470) at net.minecraft.server.MinecraftServer.y(SourceFile:605) at ph.y(SourceFile:303) at net.minecraft.server.MinecraftServer.x(SourceFile:529) at net.minecraft.server.MinecraftServer.run(SourceFile:445) at java.lang.Thread.run(Thread.java:744)Update: This crash appears to be caused by
The server crashes randomly. Most recent crash report attached.
Description: Watching Server java.lang.Error at java.util.ArrayList.indexOf(ArrayList.java:298) at java.util.ArrayList.contains(ArrayList.java:281) at java.util.ArrayList.batchRemove(ArrayList.java:700) at java.util.ArrayList.removeAll(ArrayList.java:671) at aqa.i(SourceFile:1339) at ql.i(SourceFile:470) at net.minecraft.server.MinecraftServer.y(SourceFile:605) at ph.y(SourceFile:303) at net.minecraft.server.MinecraftServer.x(SourceFile:529) at net.minecraft.server.MinecraftServer.run(SourceFile:445) at java.lang.Thread.run(Thread.java:744)Update: This crash appears to be caused by
The server crashes randomly. Most recent crash report attached.
Description: Watching Server java.lang.Error at java.util.ArrayList.indexOf(ArrayList.java:298) at java.util.ArrayList.contains(ArrayList.java:281) at java.util.ArrayList.batchRemove(ArrayList.java:700) at java.util.ArrayList.removeAll(ArrayList.java:671) at aqa.i(SourceFile:1339) at ql.i(SourceFile:470) at net.minecraft.server.MinecraftServer.y(SourceFile:605) at ph.y(SourceFile:303) at net.minecraft.server.MinecraftServer.x(SourceFile:529) at net.minecraft.server.MinecraftServer.run(SourceFile:445) at java.lang.Thread.run(Thread.java:744)Update: This crash appears to be caused by a new “feature“ called the Server Watchdog. This is a thread that kills the server when there is too much lag. Sometimes, but by no means always, this is logged accordingly:
2014-07-26 21:06:11 [Server Watchdog/FATAL]: A single server tick took 35.28 seconds (should be max 0.05) 2014-07-26 21:06:11 [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown. 2014-07-26 21:06:13 [Server Watchdog/ERROR]: This crash report has been saved to: /opt/wurstmineberg/server/./crash-reports/crash-2014-07-26_23.06.12-server.txtThanks Anthony Martin for finding this.
server crash: Watching Server (watchdog kills server on too much tick lag)
To set the server watchdog to a higher time or switch it off:Set max-tick-time in server.properties to a value higher than 60000 or to -1
http://minecraft.gamepedia.com/Server.properties#section_3
The server crashes randomly. Most recent crash report attached.
Description: Watching Server java.lang.Error at java.util.ArrayList.indexOf(ArrayList.java:298) at java.util.ArrayList.contains(ArrayList.java:281) at java.util.ArrayList.batchRemove(ArrayList.java:700) at java.util.ArrayList.removeAll(ArrayList.java:671) at aqa.i(SourceFile:1339) at ql.i(SourceFile:470) at net.minecraft.server.MinecraftServer.y(SourceFile:605) at ph.y(SourceFile:303) at net.minecraft.server.MinecraftServer.x(SourceFile:529) at net.minecraft.server.MinecraftServer.run(SourceFile:445) at java.lang.Thread.run(Thread.java:744)Update: This crash appears to be caused by a new “feature“ called the Server Watchdog. This is a thread that kills the server when there is too much lag. Sometimes, but by no means always, this is logged accordingly:
2014-07-26 21:06:11 [Server Watchdog/FATAL]: A single server tick took 35.28 seconds (should be max 0.05) 2014-07-26 21:06:11 [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown. 2014-07-26 21:06:13 [Server Watchdog/ERROR]: This crash report has been saved to: /opt/wurstmineberg/server/./crash-reports/crash-2014-07-26_23.06.12-server.txtThanks Anthony Martin for finding this.
To set the server watchdog to a higher time or switch it off:Set max-tick-time in server.properties to a value higher than 60000 or to -1
http://minecraft.gamepedia.com/Server.properties#max-tick-time
The server crashes randomly. Most recent crash report attached.
Description: Watching Server java.lang.Error at java.util.ArrayList.indexOf(ArrayList.java:298) at java.util.ArrayList.contains(ArrayList.java:281) at java.util.ArrayList.batchRemove(ArrayList.java:700) at java.util.ArrayList.removeAll(ArrayList.java:671) at aqa.i(SourceFile:1339) at ql.i(SourceFile:470) at net.minecraft.server.MinecraftServer.y(SourceFile:605) at ph.y(SourceFile:303) at net.minecraft.server.MinecraftServer.x(SourceFile:529) at net.minecraft.server.MinecraftServer.run(SourceFile:445) at java.lang.Thread.run(Thread.java:744)Update: This crash appears to be caused by a new “feature“ called the Server Watchdog. This is a thread that kills the server when there is too much lag. Sometimes, but by no means always, this is logged accordingly:
2014-07-26 21:06:11 [Server Watchdog/FATAL]: A single server tick took 35.28 seconds (should be max 0.05) 2014-07-26 21:06:11 [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown. 2014-07-26 21:06:13 [Server Watchdog/ERROR]: This crash report has been saved to: /opt/wurstmineberg/server/./crash-reports/crash-2014-07-26_23.06.12-server.txtThanks Anthony Martin for finding this.
After losing my connection to the server and logging back in, I did not appear in the player list shown when holding the List Players key (default: tab). Another player that was online could also not see me in the list. I could also not see my skin in F5 mode, the default skin was displayed instead.
However, “Fenhl joined the game” does appear in the server log.
As a workaround, relogging fixed the issue.
Update: This appears to be the result of logging in while the player is still listed as online (which happens e.g. after a “connection reset by peer” disconnect). The player logging back in does not add a second copy to the server list, and when the server catches up and removes the original copy of the player from the server list, the player is missing.
player missing from player listPlayer missing from player list
When I am receiving a status effect from a beacon, it is constantly blinking on the HUD as if it were about to run out. However, beacons provide their effects continuously as long as the player stays within range of the beacon.
I presume that the cause of this bug is that beacons provide 8 seconds of their effects every 4 seconds. Changing this to a proper continuous effect would also fix the issue where beacon effects randomly run out and restart when there is high tick lag.
Update: as of 15w36c, the effects in the HUD also randomly reorder themselves every 4 seconds.
End City spawns even without Generate StructoresEnd City spawns even without Generate Structures
On a SMP server, I am stuck in a pair of connected Nether portals. I constantly get teleported between the two dimensions, snapping back to the position of the portals even after moving. I also receive suffocation damage once per teleportation, and the change in the hunger bar and stack size after eating food only becomes visible after a dozen teleportations or so.
This happened while trying to go from the Nether to the Overworld; going from the Overworld to the Nether seems to work fine. After logging out in the Nether and asking another player (who is apparently not affected) to deactivate the portals, I tried using a different pair of portals, with the same result. I eventually died of the suffocation damage in the Overworld, and after respawning went back to the Nether to collect the part of my inventory that had fallen into the portal. After collecting the items I tried to go back to the Overworld, which triggered the bug again.
The affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz (the portals in question are those located directly at spawn, marked with yellow and green stained clay).
SMP
multiplayer (Survival/Creatie)
On a SMP server, I am stuck in a pair of connected Nether portals. I constantly get teleported between the two dimensions, snapping back to the position of the portals even after moving. I also receive suffocation damage once per teleportation, and the change in the hunger bar and stack size after eating food only becomes visible after a dozen teleportations or so.
This happened while trying to go from the Nether to the Overworld; going from the Overworld to the Nether seems to work fine. After logging out in the Nether and asking another player (who is apparently not affected) to deactivate the portals, I tried using a different pair of portals, with the same result. I eventually died of the suffocation damage in the Overworld, and after respawning went back to the Nether to collect the part of my inventory that had fallen into the portal. After collecting the items I tried to go back to the Overworld, which triggered the bug again.
The affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz (the portals in question are those located directly at spawn, marked with yellow and green stained clay).
Steps to reproduce:
- Set up a SMP server
- Give yourself the materials to build and light a Nether portal
- Enter the Nether
- Exit the Nether
May be dependent on network lag.
multiplayer (Survival/Creative)
On a SMP server, I am stuck in a pair of connected Nether portals. I constantly get teleported between the two dimensions, snapping back to the position of the portals even after moving. I also receive suffocation damage once per teleportation, and the change in the hunger bar and stack size after eating food only becomes visible after a dozen teleportations or so.
This happened while trying to go from the Nether to the Overworld; going from the Overworld to the Nether seems to work fine. After logging out in the Nether and asking another player (who is apparently not affected) to deactivate the portals, I tried using a different pair of portals, with the same result. I eventually died of the suffocation damage in the Overworld, and after respawning went back to the Nether to collect the part of my inventory that had fallen into the portal. After collecting the items I tried to go back to the Overworld, which triggered the bug again.
The affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz (the portals in question are those located directly at spawn, marked with yellow and green stained clay).
Steps to reproduce:
- Set up a SMP server
- Give yourself the materials to build and light a Nether portal
- Enter the Nether
- Exit the Nether
May be dependent on network lag.
On a SMP server, I am stuck in a pair of connected Nether portals. I constantly get teleported between the two dimensions, snapping back to the position of the portals even after moving. I also receive suffocation damage once per teleportation, and the change in the hunger bar and stack size after eating food only becomes visible after a dozen teleportations or so.
This happened while trying to go from the Nether to the Overworld; going from the Overworld to the Nether seems to work fine. After logging out in the Nether and asking another player (who is apparently not affected) to deactivate the portals, I tried using a different pair of portals, with the same result. I eventually died of the suffocation damage in the Overworld, and after respawning went back to the Nether to collect the part of my inventory that had fallen into the portal. After collecting the items I tried to go back to the Overworld, which triggered the bug again.
The affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz (the portals in question are those located directly at spawn, marked with yellow and green stained clay).
Steps to reproduce:
- Set up a SMP server
- Give yourself the materials to build and light a Nether portal
- Enter the Nether
- Exit the Nether
May be dependent on network lag.
Possible cause:
- The client spawns in the new dimension, but at the same coordinates they were before entering the portal (). If there happens to be a solid
- Then they get moved to their new coordinates, making the server think they just entered the portal
On a SMP server, I am stuck in a pair of connected Nether portals. I constantly get teleported between the two dimensions, snapping back to the position of the portals even after moving. I also receive suffocation damage once per teleportation, and the change in the hunger bar and stack size after eating food only becomes visible after a dozen teleportations or so.
This happened while trying to go from the Nether to the Overworld; going from the Overworld to the Nether seems to work fine. After logging out in the Nether and asking another player (who is apparently not affected) to deactivate the portals, I tried using a different pair of portals, with the same result. I eventually died of the suffocation damage in the Overworld, and after respawning went back to the Nether to collect the part of my inventory that had fallen into the portal. After collecting the items I tried to go back to the Overworld, which triggered the bug again.
The affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz (the portals in question are those located directly at spawn, marked with yellow and green stained clay).
Steps to reproduce:
- Set up a SMP server
- Give yourself the materials to build and light a Nether portal
- Enter the Nether
- Exit the Nether
May be dependent on network lag.
Possible cause:
- The client spawns in the new dimension, but at the same coordinates they were before entering the portal (). If there happens to be a solid
Then they get moved to their new coordinates, making the server think they justentered the portalOn a SMP server, I am stuck in a pair of connected Nether portals. I constantly get teleported between the two dimensions, snapping back to the position of the portals even after moving. I also receive suffocation damage once per teleportation, and the change in the hunger bar and stack size after eating food only becomes visible after a dozen teleportations or so.
This happened while trying to go from the Nether to the Overworld; going from the Overworld to the Nether seems to work fine. After logging out in the Nether and asking another player (who is apparently not affected) to deactivate the portals, I tried using a different pair of portals, with the same result. I eventually died of the suffocation damage in the Overworld, and after respawning went back to the Nether to collect the part of my inventory that had fallen into the portal. After collecting the items I tried to go back to the Overworld, which triggered the bug again.
The affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz (the portals in question are those located directly at spawn, marked with yellow and green stained clay).
Steps to reproduce:
- Set up a SMP server
- Give yourself the materials to build and light a Nether portal
- Enter the Nether
- Exit the Nether
May be dependent on network lag.
Possible cause:
- The client spawns in the new dimension, but at the coordinates of the entrance portal (either
MC-89928or closely related). If there happens to be a solid block at these coordinates, the player will receive suffocation damage. If the coordinates are in a lava lake, the player will catch fire.- The position gets corrected to the coordinates of the exit portal, making the server think they just entered this portal.
- If they stand in the portal for the usual 4 seconds, they get teleported back. Loading the exit dimension can cause enough lag to make it impossible to exit the portal fast enough.
Constant teleporting between Nether and Overworld(MP only)
multiplayer (Survival/Creative)Survival Multiplayer, Creative Multiplayer, Survival Singleplayer
On a SMP server, I am stuck in a pair of connected Nether portals. I constantly get teleported between the two dimensions, snapping back to the position of the portals even after moving. I also receive suffocation damage once per teleportation, and the change in the hunger bar and stack size after eating food only becomes visible after a dozen teleportations or so.
This happened while trying to go from the Nether to the Overworld; going from the Overworld to the Nether seems to work fine. After logging out in the Nether and asking another player (who is apparently not affected) to deactivate the portals, I tried using a different pair of portals, with the same result. I eventually died of the suffocation damage in the Overworld, and after respawning went back to the Nether to collect the part of my inventory that had fallen into the portal. After collecting the items I tried to go back to the Overworld, which triggered the bug again.
The affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz (the portals in question are those located directly at spawn, marked with yellow and green stained clay).
Steps to reproduce:
- Set up a SMP server
- Give yourself the materials to build and light a Nether portal
- Enter the Nether
- Exit the Nether
May be dependent on network lag.
Possible cause:
- The client spawns in the new dimension, but at the coordinates of the entrance portal (either
MC-89928or closely related). If there happens to be a solid block at these coordinates, the player will receive suffocation damage. If the coordinates are in a lava lake, the player will catch fire.- The position gets corrected to the coordinates of the exit portal, making the server think they just entered this portal.
- If they stand in the portal for the usual 4 seconds, they get teleported back. Loading the exit dimension can cause enough lag to make it impossible to exit the portal fast enough.
Workaround:
Log out and back in while you are in the correct dimension. Note that when doing this you can occasionally find yourself at incorrect coordinates.
"credits.ogg" (Named "Alpha" in C418's Volume Beta) does not play upon viewing the credits after entering the portal created by killing the Ender Dragon. The end poem can remain silent through the entire 10 minutes.
On rare occasions the track may play, but plays at the incorrect time and cuts out when the credits finished. I once had it just start to play at the "Twenty years from now..." quote, which is the very end of the poem.
(This ticket was originally reported by
"credits.ogg" (Named "Alpha" in C418's Volume Beta) does not play upon viewing the credits after entering the portal created by killing the Ender Dragon. The end poem can remain silent through the entire 10 minutes.
On rare occasions the track may play, but plays at the incorrect time and cuts out when the credits finished. I once had it just start to play at the "Twenty years from now..." quote, which is the very end of the poem.
(This ticket was originally reported by
"credits.ogg" (Named "Alpha" in C418's Volume Beta) does not play upon viewing the credits after entering the portal created by killing the Ender Dragon. The end poem can remain silent through the entire 10 minutes.
On rare occasions the track may play, but plays at the incorrect time and cuts out when the credits finished. I once had it just start to play at the "Twenty years from now..." quote, which is the very end of the poem.
(This ticket was originally reported by Sebastiano La Gala.)
~~"credits.ogg" (Named "Alpha" in C418's Volume Beta) does not play upon viewing the credits after entering the portal created by killing the Ender Dragon. The end poem can remain silent through the entire 10 minutes.
On rare occasions the track may play, but plays at the incorrect time and cuts out when the credits finished. I once had it just start to play at the "Twenty years from now..." quote, which is the very end of the poem.~
(This ticket was originally reported by Sebastiano La Gala.)
~~"credits.ogg" (Named "Alpha" in C418's Volume Beta) does not play upon viewing the credits after entering the portal created by killing the Ender Dragon. The end poem can remain silent through the entire 10 minutes.
On rare occasions the track may play, but plays at the incorrect time and cuts out when the credits finished. I once had it just start to play at the "Twenty years from now..." quote, which is the very end of the poem.~
(This ticket was originally reported by Sebastiano La Gala.)
"credits.ogg" (Named "Alpha" in C418's Volume Beta) does not play upon viewing the credits after entering the portal created by killing the Ender Dragon. The end poem can remain silent through the entire 10 minutes.
On rare occasions the track may play, but plays at the incorrect time and cuts out when the credits finished. I once had it just start to play at the "Twenty years from now..." quote, which is the very end of the poem.As of 1.9-pre3, the credits screen is skipped entirely.
(This ticket was originally reported by Sebastiano La Gala.)
Iron golem attacking players on peaceful difficulty, but attack does not hurt player
Steps to reproduce:
- Summon an iron golem (
/summonVillagerGolem)- Make sure you're in Survival mode
- Attack the golem
- The golem will repeatedly swing its arms at you, but you won't receive any damage or knockback
Steps to reproduce:
- Set the difficulty to peaceful (/difficulty 0)
- Summon an iron golem (/summon VillagerGolem)
- Make sure you're in Survival mode (/gamemode 0)
- Attack the golem
- The golem will repeatedly swing its arms at you, but you won't receive any damage or knockback
I would expect the golem to either deal damage or not swing its arms at all.
Do notmove the cursor whenthe game gets automatically pausedCursor moved to center of screen when game gets automatically paused
1. Open a new world
2. Alt-tab to another program (or use windows key to open the start menu)
3. Minecraft is no longer in focus
4. As soon as auto pause kicks in, cursor will be moved to dead center on the screenSteps to reproduce on OS X
- Disable auto-pause using F3+P
- Stand in a Nether portal
- Switch to another fullscreen app
- As soon as the Nether loads, the cursor will suddenly be in the center of the screen.
This can be very annoying as it can lead to clicking on things you didn't intend to in any app.
Steps to reproduce on Windows
- Open a new world
- Alt-tab to another program (or use windows key to open the start menu)
- Minecraft is no longer in focus
- As soon as auto pause kicks in, cursor will be moved to dead center on the screen
Steps to reproduce on OS X
- Disable auto-pause using F3+P
- Stand in a Nether portal
- Switch to another fullscreen app
- As soon as the Nether loads, the cursor will suddenly be in the center of the screen.
(This ticket was originally reported by xPaw.)
Windows 10
, single-player world.Windows 10 or OS X
When spectating from the perspective of a hopper or furnace minecart, the camera is pointing in a seemingly random direction instead of the direction the minecart is moving.
2016-04-17_14.15.16.png
Windows 7 64bit, Java 7 (1.7.0_09)
Windows 7 64bit, Java 7 (1.7.0_09)
OS X 10.11.5, Java 8 (1.8.0_74)
When I open my inventory and go to the search tab, I enter something in and everything goes wonky. I am done searching so I press backspace and the entire search term disappears. I enter the chat to say hi to my friend who just joined, I misspelled his name and I tried deleting the accidental character, and the entire name disappears. Say his name was George, and I type Goerge instead. I would press backspace, and all "Goerge" would disappear. (Get what I mean?) This happens until I completely re-start the game.
Delete whole word: CTRL is stuck, delete whole line: SHIFT is stuck.
Steps to reproduce on OS X:
- have Minecraft and at least one other app open in fullscreen mode
- open chat, type a few letters
- holding ⌘, switch the other fullscreen app by swiping left/right with 4 fingers on the trackpad (⌘⇥ also works if you press ⌘ quickly enough while the app switch animation is active)
- release ⌘
- switch back to Minecraft
- press A. This will select the text you typed instead of writing the letter A.
Ubuntu Lucid Lynx (10.04) LTS
Architecture: i686
CPU op-mode(s): 64-bit
CPU(s): 1
Thread(s) per core: 1
Core(s) per socket: 1
CPU socket(s): 1
Vendor ID: AuthenticAMD
CPU family: 15
Model: 76
Stepping: 2
CPU MHz: 800.000
Kernel version: 2.6.32-45-generic
Fenhl (Max Dominik Weber), I can't confirm this. For me, it's playing the right track, Alpha (credits.ogg).
Tested it some times and confirmed a lot of weird things.
- First test: Before entering the portal, the End track started playing. When I entered the portal, the End music didn't stop; some seconds later, the Credits one started; and finally, both songs stopped abruptly and the credits became silent. After that, every music in the game stopped playing, in the menu, in the overworld, in the end, and in the credits as well. They only started playing again after restarting the game.
- Second test: After restarting the game and trying again (this time with no End music), the credits music stopped after the first note was played.
- Third test: With the End music playing this time, after entering the portal the End music stopped, but instead of the credits one starting, the End one started again instead, and the credits were played with this track (what Fenhl (Max Dominik Weber) was experiencing).
- Fourth test: With the End music playing again, after entering the portal, the End track stopped, the credits one started, and I thought everything was right, but I could hear a noise in the background, which was the End track starting again, which caused the credits to be played with both tracks at the same time. And after quitting the credits, both songs continued playing in the overworld! And after quitting the game, both songs still played in the game menu! (I really needed to record this one, there's a video here.)
As we can see, there are still a lot of weird behaviors, and the sound engine is terribly messed up (sorry Searge, I think you didn't fix anything). Hope we can figure out if there's still something wrong left, because this is an annoying bug. For now, please reopen this ticket if you mods get to confirm this behavior.
![[Mod] Sonicwave](../../../data/avatars/users/94627.png){kind=small}
Could this issue be related to MC-35714 and/or MC-35856? From Bentroen's and Fenhl (Max Dominik Weber)'s comments the game is either playing the End music again, playing both at the same time, or not playing at all.
@Fenhl (Max Dominik Weber): This is most probably MC-85285
@Fenhl (Max Dominik Weber): Outdated Graphics card drivers
OpenGL: Intel HD Graphics 4000 OpenGL Engine GL version 2.1 INTEL-10.6.31, Intel Inc
Intel HD Graphics 4000 is supporting OpenGL 4.0 whereas your driver only supports OpenGL 2.1, see e.g. crash report of MC-84984:
OpenGL: Intel(R) HD Graphics 4000 GL version 4.0.0 - Build 9.17.10.3114, Intel
@Kumasasa: I didn't test fresh worlds and have no interest in doing it, but it definitely affects old worlds in 15w42a. The affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz
It occasionally happens while entering the end. It also happened to Fenhl (Max Dominik Weber) as described in the comments to MC-90605 while entering and exiting the nether.
Thanks, ticket is now Fenhl (Max Dominik Weber)'s.
Fenhl (Max Dominik Weber), can you confirm this is still happening in recent 1.9 snapshots ?
Fenhl (Max Dominik Weber): Create a new report please.
edit: MC-92588.
@Fenhl (Max Dominik Weber): Sounds like MC-97540.
Changed reporter to Fenhl (Max Dominik Weber) please keep this report up to date
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
Fenhl (Max Dominik Weber), could you please create a new ticket for that?
In case you're on a server, perhaps MC-190098 describes your issue?
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
Can reproduce this in 24w04a. I'd like to request ownership of this issue, as it relates closely to another issue I maintain, MC-234511. Fenhl (Max Dominik Weber) has also been inactive for 4 years.
Still happens in 1.4.7
Also applies to pushing sideways.
Still occurs in 1.5.1
Additionally, using a spawn egg on a block to the northwest of the player has no effect, while using one on an animal to breed it works, but only if the parent has moved since the player has teleported. Similarly, newly-spawned animals in the affected area cannot be attacked until they have moved.
Also happens in the “Edit Server Info” screen (or at least when adding a new server).
Please reopen: As of 13w18c this affects unmodded Minecraft with any texture pack including default.
Affects snapshot 13w18c.
I repeat: This is not a duplicate of
MC-17831and is still present in 13w25a.MC-18035(which is marked as a duplicate of this) is not fixed in 13w25a.Yes.
Still happens in 13w26a.
Case a seems to have been fixed, the other two still apply.
As mentioned in duplicate
MC-21543(which was reported asMCL-162), this occurs independently of Minecraft version when using the new launcher, and never occurs when using the old launcher, also independently of Minecraft version.I have now noticed that the crash does not occur with another resource pack (oCd).
If you unzip the resource pack, it will show up. I have changed the description accordingly. Please reopen.
I can confirm this in Minecraft 1.6.2 on OS X.
This also occurs when players enter the End, although in this case they are always offset by one meter on the y coördinate: they appear to be floating one block above their actual position.
Still occurs in 13w36a.
Affects snapshot 13w36a.
Affects snapshot 13w36a.
Affects snapshot 13w36a.
Strange, the circumflex actually does work for me.
I think it's dependent on the keylayout. I'm using an English/International hardware keyboard with a custom keylayout that puts ä on alt-A, ß on alt-S, etc.
Yes, it's a launcher bug. See this comment.
Affects 13w37b. For me, the server didn't crash, but instead kicked me with “end of stream”. The other players were fine. I could not reconnect, receiving “end of stream” on each attempt. Restarting the server resolved this. The lamp seems to be missing, although it could have despawned naturally.
@Atom clark: Have you actually got the achievement without visiting Frozen Ocean and Extreme Hills Edge?
This affects 13w38c, and is especially annoying with all the invalid blocks generated by bug in 13w38b (such as
MC-31883).Looks like this is fixed in 13w38c.
Seems to be fixed in 13w38c: nights are still laggier than days, but it's not noticeable anymore, at least on a decent server.
Affects snapshot 13w38c.
This has not been fixed, it still occurs in 13w41b. Please reopen.
@Markus Haberstock: That is a separate bug,
MC-31006. Even when the game is left open from beginning to end (and thus,MC-31006does not apply), this bug still applies.I play on the same server, and only had a single lagspike so far, and the mob farm was outside my view distance (bot server-side and client-side) at the time. Not only did the FPS drop, animations (such as enchantment glow and view bobbing) also slowed down. Restarting Minecraft solved the issue for me. This seems to point to a client-side problem.
Affects 1.7.2
Affects snapsnot 13w47c.
Affects snapshot 13w47c.
Affects snapshot 13w47c.
Affects snapshot 13w47d.
I can't update the affected versions field, but yes, it still is an issue in snapshot 13w47d.
Please reopen, this is still an issue in 13w49a, even in singleplayer. Can be easily shown in CSP by creating a new superflat world with render distance set to 16, then flying up. Chunks will stop generating while still within the render distance, making the edges clearly visible.
For me, the chunks loading does not resume when letting go of the jump key. Also, when staying on the ground for a while and then flying up, the loaded chunks clearly form a square, as opposed to the circular shape of the distance fog.
This bug appears to be fixed in the 14w02c snapshot.
May be a duplicate of
MC-36883.Mods, please re-check. This is very obviously not a duplicate of
MC-46408.Can reproduce: Mac OS X 10.9.1, Intel HD Graphics 4000 1024 MB
For me, the effect only occurs when the enchanted item is in the last non-empty inventory slot.
You're not actually rendered as standing, your sitting position is just too high.
Affects snapshot 14w06b.
I did the following to confirm that the bug still exists:
I did not get the achievement. If anyone can find an error in my test, please say so.
I have attached my .minecraft/saves/Adventuring Time Test/stats/Fenhl.json, both the unmodified version from after I exited Minecraft (Fenhl.json.orig) and a formatted version for easier reading (Fenhl.json).
On OS X, there is a workaround if you're in native fullscreen (see MC-40597): switching to a desktop or a different fullscreen app (at least using the touchpad gesture, other methods like keyboard shortcuts not tested) will activate the pause menu.
Affects snapshot 14w08a.
Affects snapshot 14w08a, and also with the stat.damageTaken statistic.
I have repeated my test in 14w10c and a new world with the same seed, still no achievement. A definitive list of exactly which biomes (id, name) are supposed to be required for the achievement would be very helpful for further debugging.
Also affects signs.
Also affects the multiplayer server list. A workaround is to scale up the UI and/or resize the window until the list needs a scroll bar. When there's a scroll bar, it will stop flickering.
Affects snapshot 14w11b.
Affects snapshot 14w11b.
No longer an issue because LC value is no longer displayed in the client.
Affects 14w11b and not a duplicate of
MC-2931. Please reopen.Unlike JungleEdge M (which does generate), FrozenOcean and Extreme Hills Edge are confirmed not to generate in 1.7 or higher. This second issue might however be fixed in the snapshots already, I'll try teleporting to all the biomes you listed minus these two and will report back on whether that triggers the achievement.
Negative. Affects 14w11b.
Andrés del Campo Novales: The latest snapshot is the version we're supposed to be testing bugs in, so I'm assuming Markus Haberstock is referring to 14w11b.
Mojang has explained on multiple occasions that letting the community contribute fixes is impossible due to copyright/licensing issues. That said, it would be nice if they took the time to change a single character in order to fix the game's achievement system. That is, of course, unless the “fix one bug, encounter a new one” pattern that has been going on with Adventuring Time continues after this.
Our Java is up-to-date: as you can see here, the version number matches what is installed on our server.
Please reopen.See below.Fixed in 14w17a.
user-f2760 The bug here is that players and mobe suffocate even when inside the worldborder. Curiously, this only happens once the border is set via the command.
Talven81, are you sure that mobs and players suffocating inside the worldborder is intended?
This issue is a duplicate of
MC-53381.[Mojang] Grum (Erik Broes): have you heard back from LWJGL yet? If not, it might be better to just remove the F11 shortcut, as suggested by Finn Wilke.
The glitch only occurred a single time, so I can't say if it's fixed or not.
Dlawso the Really Lucky Rabbit: Can you provide a source on your claim? It certainly seems like a bug to me.
This issue is specifically about expanding borders, not shrinking borders.
PappaDavid: No, that actually just means that it will be fixed in the next 1.8 snapshot.
@Itouch2: This is not a duplicate of
MC-46776. Instead it is a bug that was introduced by that bug's fix. Please reopen.To illustrate what is wrong here, try this:
I opened
MC-54556for the issue I described.Updated title and description accordingly.
Affects 14w20b (noticed in title screen).
@Calvin Stromwall: The problem here is that you can fall of a cliff if you sneak off a chest which is on the edge of that cliff. You fall off the chest because the drop is less than a block, but sneaking speed is still fast enough to have you miss the block and fall off.
I fail to see how this is not a MCL bug, but yeah.
Works for me now.
Affects 14w25b: after the server runs for a while, everyone is kicked and then no one can join anymore, getting this exception instead.
@Bobby Jones: The server is still running, and using the list command from the console reports the player(s) who were online at the time the error occured as still online.
@Shaun Holt: I don't think your issue is the same as this one. You might want to open a new issue for it.
It does affect all redstone torches, but only if there is no block under the torch.
Affects 14w26c. The invisible characters no longer take up space in signs (because the amount of characters fitting in a line is determined by their width now), but they are still in there, and hitting backspace will not delete letters because it deletes the invisible character instead.
That link is broken. Try this one instead:
MC-59856I thought adding a custom log4j configuration would fix this, but no such luck.
@Joona-M Heikkilä: That's probably unrelated.
Is this purely visual, or do existing repeaters change behavior?
Duplicate of
MC-60151, and it is purely visual.Also affects iron trapdoors. Does not affect the collision box.
For me the numbers are different but otherwise it's the same error message. Other players can join the server just fine, it's just me who can't log in. Our world doesn't have any barrier blocks in it.
Possibly related to
MC-61329Update: the error occurs only on one of two servers I have tested. It occurs on a Survival server but not on the associated Creative server. After being disconnected from the Survival server with this error and joining the Creative server, the chat displays a welcome message from the Survival server in the chat. Leaving and reconnecting to the Creative server makes the welcome message disappear.
Both are vanilla servers, the welcome message is provided from an external program instead of a server mod.
Workaround: Restarting the server seems to have fixed the issue for me.
Edit: nope. That just replaced this bug with
MC-61338and the next server restart replaced that bug with this one again.Affects 14w28a.
cannot confirm, it's fixed for us
The reverse happens when blocks are placed. The hitbox appears instantly but the block model takes a while, and sometimes doesn't appear for several minutes.
Also happens in Survival.
F3+A does not work for me.
Please reopen. Happens again in 14w30b.
About a dozen crashes later, I am fairly certain that the crash happens when a certain part of the Nether is unloaded, ~30 seconds after using a specific portal to the Overworld. The region of the Nether in question has a
MC-15019style item dupe in it, so the same bug that causes the dupe may be responsible for this crash.Okay, so what I described above is only one very specific cause of a much more general problem. Loading and unloading the Nether causes lag, and the watchdog kills the server when there's too much lag. I can see why a behavior such as this could be desirable, but in my opinion the threshold is much too low and the watchdog should be optional.
@[Mod] CubeTheThird: It doesn't seem intended, and it is certainly not very usable. I think this issue should be reopened since part of what it says in the title isn't fixed, and it should be up to the devs to either fix it or mark it as intended.
Those are a different issue.
Affects 1.8-pre3.
Why is this closed as invalid? I just received a similar exception. Affects 1.8-pre3.
Affects 1.8, at least for killing iron golems.
Affects 1.8.1-pre3.
I have only experienced the bug twice, so I can't say if it's fixed or not. If this happens to anyone in a current version, leave a comment and I'll update the affected versions accordingly.
I can't update the affected versions field, but yes, it affects 1.8.1-pre3 and OS X 10.10 Yosemite.
It's not just item entities. While playing the Arena branch of qmagnet's Diversity 2 in 1.8, I noticed that some of the mobs randomly turned invisible after a respawn. They would automatically reappear after a while, usually after already having attacked me.
Affects 1.8.1-pre4, please reopen.
Joshua Mack's workaround is ineffective, as is relogging. Relaunching the Minecraft client fixed it for me.
I just tested this in 1.8.1-pre4, and not only was the credits music not playing, the End music kept playing when the credits started. This suggests that there's a “stop all current music and play the credits music instead” trigger missing.
I just had Moog City 2 and Mutation play at the same time after being disconnected from a server due to network timeout (train went into a tunnel). Affects 1.8.1-pre5, please reopen.
Affects 1.8.1.
Affects 1.8.1, at least for dark oak.
Why is this only marked as “relates to
MC-73302”? It should be closed as duplicate.Just happened to me in 1.8.1 after leaving a server normally, so it's not just forced disconnects. And why is this not reopened yet?
Affects 1.8.2-pre1, at least for killing iron golems.
Just tested and it played The End instead of Alpha. Affects 1.8.2-pre4, please reopen.
Affects 1.8.2-pre4, at least for killing iron golems.
Affects 1.8.2-pre4. Possibly related to the fix of
MC-14671.Also affects arrays of comparators.
Affects 1.8.2-pre6.
Affects 1.8.2-pre6, at least for killing iron golems.
Affects 1.8.2-pre6. Why is this not reopened?
Duplicate of
MC-77055.Affects 1.8.2-pre6.
Affects 1.8.7.
@Afootpluto: I don't have any McAfee products installed.
Affects 1.8.7.
Affects the 1.8.8 pre-release.
MacBook Air (13 inch, Mid 2012)
OS X 10.10.4
java version "1.8.0_40"
Java(TM) SE Runtime Environment (build 1.8.0_40-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
This ticket is falsely marked as a duplicate of another ticket which is closed as invalid due to use of server mods. However, the issue also occurs on vanilla snapshot servers, even without any resource packs. Please reopen.
Affects 15w31a. Why is this not reopened?
This ticket is incorrectly closed as a duplicate of a ticket which states that an error occurs on the server side. This issue occurs even without an error on the server side, on every connection attempt, by every player, on two servers I have tested. Please reopen.
Duplicate of
MC-82968.[Mojang] Searge (Michael Stoyke) seems to be aware of the issue: https://twitter.com/SeargeDP/status/626414559100829696
Affects 15w31b, even with a world loaded from a 1.8.8 backup.
Could you please clarify which issue you are referring to?
@Anthony Martin: Please stop constantly editing your post. 13 people are receiving an email each time you do. The preview feature exists for a reason.
Affects 15w31c, even with a world loaded from a 1.8.8 backup. No signs were created using commands on this world.
It's marked as fixed for the next snapshot, you don't need to confirm it anymore.
Affects 15w31c. Especially annoying with items held in the left hand (no matter the main hand setting).
Affects 1.8.8 and 15w31c, on OS X 10.10.4. Dead keys are completely ignored. Tested with U.S. and a custom keylayout on an English/international hardware keyboard.
Affects 15w32a.
This occurred when we updated our server to 15w32a directly from 1.8.8, and tried to connect with 15w32a clients. Our world can be downloaded at http://wurstmineberg.de/assets/latestbackup.tar.gz (note that this is the 1.8.8 backup).
We updated out server from 1.8.8 to 15w32b, and all the named Creepers at our charged Creeper farm (none of them were actually charged yet) despawned, along with a named zombie nearby. A named skeleton directly next to spawn survived the update.
Affects 15w32b.
Title is incorrect, also affects minecarts.
Upon further testing, it appears that when a player enters the End exit portal, all entities which are within view distance of spawn but not in the spawn chunks are deleted.
No, I always start Minecraft normally, which on OS X means that trying to start it while it is already running will do nothing.
First question: if by any snapshot you mean any 1.9 snapshot, then no. However, the world has previously been loaded in snapshots for older versions.
Second question: no.
As previously stated, no.
The issue slows down the entire system while the Minecraft client is open, even in the main menu.
Attached my force-crash log.
@Kumasasa: First of all, the ticket you are linking to is closed as invalid due to modding. I am not using mods. Also, more importantly, I am on the latest driver, since graphics driver updates for OS X are distributed through the App Store, and the App Store shows no available updates.
Affects 1.8.8.
Affects 15w32c. Are any of the mods still reading this? If so, could you please explain what's going on?
Affects 15w33b.
Affects 15w33b, and perhaps the summary and/or description should be updated to include at least some mention of the Unbreaking enchantment?
Fixed in 15w33b.
Affects 15w33c. Will try to reproduce.
Was able to reproduce in SSP, so it affects both single- and multiplayer. Steps to reproduce:
Affects 15w35b. I was unable to find a related issue on the LWJGL issue tracker.
Affects 15w35b.
@PanchamBro: that is
MC-40275, which seriously needs to be reopened.@KingSupernova: have you read
MC-40275's comments? I have, on multiple occasions. No reaction from any of the mods.Thanks for reopening. I tested after making sure I had the music at 100% and could actually hear other music, and was still able to reproduce. Affects 15w35c.
Affects 15w35e. Currently playing: Moog City 2 and Moog City 2, but with a delay.
Affects 15w35e. Another player and myself are constantly kicking each other off the server, getting the same error (except with different numbers). Server log shows the same error messages.
The issue only seems to occur when the players are within viewing distance of each other.
You're right, it only happens around spawn. Two players being within view distance of each other in the affected area is also a requirement for the bug to trigger though.
Some observations: let's say player A is in the affected area.
When player B moves into view distance of player A (e.g. using a Nether portal), both are kicked.
When player B logs in within view distance of player A, usually only player A is kicked, but sometimes both are kicked.
This plus the Netty-related exceptions point towards the error being related to the Spawn Player packet.
Affects 15w35e.
There are no command blocks in our affected world.
For reference, the affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz. The two farms at spawn causing the bug are turned off and can be turned on by flicking the levers at 44 114 -10 and -69 70 -5.
The affected area contains signs that have previously been affected by
MC-82968andMC-85627, but another area which also has these signs appears to be unaffected.Affects 15w36c, please reopen.
Affects 15w36c.
Attached the game output log, copied while the client was hanging. The disconnect exception found in the log has been reported as
MC-87041.Also affects OS X when Mission Control is activated while loading a world. Moving the cursor is not possible until Mission Control is deactivated.
Affects 15w37a.
In our case, the cause is a mob farm at spawn, whose water flushing system causes a heavy amount of block updates every few seconds. After disabling the clock, multiple players can be online at spawn at the same time again.
I just heard Alpha in the Minecraft credits for the first time. However, it was also playing The End at the same time. Affects 15w37a.
Affects 15w37a. Can also be reproduced by eating a pufferfish, then drinking milk.
Affects 15w38b.
Affects 15w39c. As a workaround, if breaking and replacing all hopper minecarts is too much work, the following command will fix all currently loaded hopper minecarts:
/entitydata @e[type=MinecartHopper] {Enabled:1b}Affects 15w39c. Once again, only The End played.
Affects 15w40b.
Affects 15w40b.
Affects 15w40b.
Affects 15w41b.
Affects 15w41b, please reopen.
For the record,
MC-89127is a duplicate of this and has been reopened.this is a duplicate of
MC-87041, but that one has been erroneously marked as fixed.Same with the other one. And the part before the slash in the server logs is just the origin thread.
That claim appears to be based on the numbers being different in the error messages. The problem is exactly the same though: large amounts of block updates in areas with more than one player kick some or all of these players.
The steps given above no longer work to reproduce the bug, both because the offending dogs which were located at felis' and madmalik's base have been edited out of the world, and because of
MC-89928.Fixed in 15w42a, at least in SSP.
I have not been able to reproduce in Singleplayer either.
I tested it with a different account to try and see if it was somehow account-related, but this time going from the Overworld to the Nether triggered the teleport loop. I changed my gamemode to Spectator to break out of the teleport loop and found myself in the Nether, but at the coordinates of the Overworld portal. Which probably means that this bug is related to
MC-89928.Affects 15w43b, tested in a newly created world. Please reopen.