mojira.dev

0x5e3371ebe11e

Assigned

No issues.

Reported

MC-249585 Minecraft identifies as "java" to pulseaudio on Linux Community Consensus MC-249570 Default audio device selection broken and Minecraft fighting back against external audio device change on Linux + Pulseaudio Awaiting Response MC-227891 Ender pearls despawn when player logs out of a server Fixed MC-92689 Revert comparator behavior to not break existing contraptions! Duplicate MC-88647 Glitchy spiders hitting through wall Duplicate MC-88646 Spider Jockeys are broken - skeleton does not move Fixed MC-88645 Vines are not being placeable at all Duplicate MC-66127 Commands cannot target mobs that went through a portal Duplicate MC-56008 Player joining game twice: Item + Horse (any ridable entity) Duplication + Confusing Statistics & Achievments Duplicate

Comments

This also affects the search item tab in the creative inventory screen, randomly writing an 'e' into the search bar when opening it.

This bug does not only affect the first player that enters the game. After about two weeks of running a busy server, the entity IDs will overflow, which results in no player being able to use fireworks. Negative entity IDs are also ignored by this function (from 1.12.1 decompiled with MCP):

public boolean isAttachedToEntity() {
      return ((Integer)this.dataManager.get(BOOSTED_ENTITY_ID)).intValue() > 0;
   }

What is this nonsense, and why did this get 'fixed'? The comparator never worked this way. If you put buttons/levers/torches anything next to it, it dosn't turn off. Only redstone dust could be used for the compare input. Why should it be different with redstone blocks? I think actually "fixing" this bug is a far worse bug, this should get reverted!