Ozone Smith
Assigned
Reported
MC-200578
Volumetric target selectors create a strange bounding box
Duplicate
MC-123628
Unexpected behavior when using "execute store success score" with a function
Fixed
MC-122519
if block argument in /execute does not work correctly
Invalid
MC-105920
"score_..." and "score_..._min" parameters with a dash in the objective are not counted
Duplicate
MC-104853
Semi-transparent pixels in the hat texture of a head block the view of other blocks on heads.
Duplicate
MC-96597
hoverEvent and clickEvent are one line lower than they should be.
Duplicate
MC-93844
Transparent hat pixels on skull render opaque
Fixed
MC-93419
Non-Opped Players cannot place blocks with BlockEntityTags
Works As Intended
MC-92266
Dead mobs are not removed from their teams
Fixed
MC-92264
When scoreboard.dat file is over 2.2 mb, server becomes unjoinable.
Community Consensus
MC-91012
Server item duplication
Duplicate
MC-90711
Marker ArmorStands cannot be selected within r=0
Fixed
MC-89652
Using a solitary cuboid selector (x & dx, y & dy, or z & dz) with @e only selects players
Invalid
MC-89358
Right-Clicking a spawn egg on a spawner doesn't always overwrite SpawnPotentials
Duplicate
MC-89220
Buggy conditionality when command blocks are updated within a tick
Works As Intended
MC-87956
If a spawner's delay is 0, right clicking with a spawn egg on it doesn't change the id.
Fixed
MC-87945
Command blocks switching on in weird order
Duplicate
MC-87941
Server console regularly reporting 2 errors
Duplicate
MC-87531
Chain command blocks activating under incorrect conditions
Invalid
MC-86592
Mac keybinds not reading properly when in a different keyboard layout
Duplicate
Comments
Seems to have been fixed as of 18w01a; "result" may still be odd, but "success" seems properly isolated.
I seem to have accidentally created this in the WEB section. Sorry, was not intended, would someone please move this to the Minecraft project?
I did indeed read it carefully, and it matched what I had read in the update notes. If such information is, in fact, wrong, so be it.
Works as Intended.
The start depletion was listed in the 1.9 update logs.
One hopes that will change.
Under the new selector order, seems fixed.
Did some more digging; It seems to be caused by the "assets" tag in the <version>.json file in versions/<version>/. If that's missing, you get the aforementioned erratic boot.
It seems to be rather erratic, as I got a lot of "Missing sound event for thing.subthing" logs when booting 1.9-pre3.
Confirmed.
Yeah, I've seen this as well.
This is still an issue even though r=0 now does r=0.25.
Apparently, r=0 is totally broken now.
Gads, this bug is annoying.
Still present in 16w05b.
I know that, but it's a nice visual log.
Confirmed for 16w04a.
Confirmed for 16w03a.
Command: /summon ArmorStand ~ ~1 ~ {CustomNameVisible:1b,DisabledSlots:2039583,HandItems:[{id:"stone_slab"},{id:"stone_slab"}],ArmorItems:[],Marker:0b,Invisible:0b,Invulnerable:0b,NoBasePlate:0b,NoGravity:0b,Pose:{LeftArm:[0f,0f,0f],RightArm:[0f,180f,0f]},ShowArms:1b,Small:1b,CustomName:"",Tags:[]}
I haven't checked recently.
This got fixed, somehow.
I don't know, as since the removal of MC-92266 it's extremely difficult to replicate.