Spake Miner
Assigned
Reported
MC-106464
Custom sounds suddenly disabled
Awaiting Response
MC-105728
Marker armor stands go through walls
Works As Intended
MC-103462
Some translucent parts of entities are rendered behind translucent blocks, block entities and some entities (depending on loading order)
Fixed
MC-102598
/tping entities results in teleportation relative to the player
Fixed
MC-96565
Entities with NoAI no longer ignore the Motion tag
Works As Intended
MC-96024
Leads in unloaded chunks break, become invisible or connect to an invisible target far away
Duplicate
MC-91305
Fake players in scoreboards don't show up when the display of the objective is in 'list'
Invalid
MC-90822
A player with Elytra's camera position changes when sneaking while in midair
Duplicate
MC-90747
Block placing is glitchy for LAN guests
Incomplete
MC-90746
Sometimes placing command blocks in certain positions causes lag spikes
Incomplete
MC-90703
Blocks on head don't rotate horizontally for other players
Invalid
MC-90621
Command blocks sometimes don't load their GUI for LAN guests, even after long periods of time
Duplicate
MC-90333
Constantly executing /tp ~ ~ ~ glitches your position
Duplicate
MC-89783
Items on locked hoppers don't get in the hopper after it was unlocked
Duplicate
MC-89729
Rarely, you'll hear the sound 'minecart.base' when opening a world
Duplicate
MC-89701
Giving a guardian NoAI while he is charging his laserbeam freezes the laserbeam
Invalid
MC-89567
Chunks errors are extremely common in multiplayer
Incomplete
MC-89469
Sometimes players are not invisible even under the invisibility effect
Incomplete
MC-89332
Snowballs sometimes hit the player that threw them
Duplicate
MC-89253
Bold text in /tellraw combined with links positioned incorrectly
Awaiting Response
Comments
Well, it just says
[00:31:54] [Client thread/INFO]: Reloading ResourceManager: Default, resources.zip
By the way, it's a resource pack put on a map. Also, this message appeared when the map was loaded and the sounds did play successfully. I'll try to reproduce this tomorrow with more detailed results (possibly including a crash report), but there's a chance that it won't work since I haven't had this glitch ever before and it seems really rare.
Marker armor stands have a hitbox at a size of 0. There is nothing said about collision.
...what?
So the fact that it's a marker means it should go through walls?
Honestly, I don't think this deserves to be a duplicate. Someone please reopen this. The whole purpose of barrier blocks is to be 100% invisible but at the same time solid. What this bug does is ruin the whole purpose of the block; Now from being invisible, you can clearly see it underwater. Yes, barrier blocks are also transparent and all transparent blocks have that thing underwater, but since barrier blocks are a special type of block, I think it deserves a special behavior. And don't get me started on how this sounds like a suggestion, because Minecraft Wiki literally says this so:
"A barrier is an invisible block which appears transparent, but has mixed properties."
Confirmed for 1.10. The glitch, however, is different than what the ticket says; The glitch is that actually two players in a ladder together start going up, not getting stuck.
There's something about this ticket I don't understand. It's fairly popular (43 votes and 28 watches), it has Searge assigned to it, it's pretty major, it's fairly old, it's related to 2 tickets and is duplicated once, yet it's not yet fixed and its Confirmation Status is on "Community Consensus". I mean, what? It's getting a lot of attention but nobody's actually doing anything about it?
Okay, thanks I guess.
Alright, this has been a bug that's been bothering me forever, so I'm going to reply instead of the ticket's creator: Yes, this bug is still happening since then, even now in 1.10.2. Always been there, never fixed, caused tons of issues. Please open this issue.
Uh... This is a joke... Right?
Well, if not, a server crashing isn't a Minecraft bug, but rather an issue with the server itself.
Agreed, needs exact commands.
Confirmed for 1.10.
Confirmed for 1.10. Why the hell isn't this bug fixed yet?!
It needs to be turned off, not on.
Can confirm, but I'm pretty sure there's already a report of this issue. Can't find it at the moment though.
Bump; Definitely not fixed. Confirmed for 1.10.
Yep, also an issue in 1.9.4.
Okay, going to now.
Confirmed for 1.10.
Might be.
Confirmed for 1.10.2.