mojira.dev

stop.x

Assigned

No issues.

Reported

MC-123189 There are gaps between grass block texture Duplicate MC-123019 Type /execute if block and then type space crashes the game Duplicate MC-114923 Sound is played ignoring player's y coordinate Cannot Reproduce MC-103075 /fill air with destroy key word does not counted as success in command blocks Duplicate MC-102853 Player's inventory display bug Duplicate MC-102678 scoreboard new criteria stat.killEntity.Husk, ...Stray, and ... WitherSkeleton not working Invalid MC-102673 \n in title json creates strange character instead of starting a new line Invalid MC-95880 Entities can break the lead themselves Duplicate MC-95366 /playsound command plays incorrect sound Invalid MC-94546 Achievement "overpowered" requirement unchanged and unobtainable Invalid MC-93717 Can't remove off-hand items by pressing F Fixed MC-92621 Slime movement and path finding bug Works As Intended MC-92035 When breaking or replacing a hole on the last layer, game stuck Duplicate MC-90948 When elytra is functioning, levitation effect does not function at all Duplicate MC-90296 Written books cannot be tested with pages tag Invalid MC-90065 Trade with customised villagers cause game crash Duplicate MC-88990 Inventory bug when riding on a entity horse without a chest Duplicate MC-86416 Zombies don't try to follow and attack players when players are in water Fixed MC-95513 Using /fill command for large range causes game stuck or a crash Duplicate

Comments

Enchantment id is a short tag, not a string tag. Use numeric id.

confirmed for 1.10 pre-2

It seem to be normal again, after I tested a few commands. Can't figure out what went wrong

I have the same problem with my current save game. It does not occur in all worlds but one which is a "void" type superflat world with a lot of command blocks in it.

r=0 now means exactly same position. Use r=1,c=1 instead.

Ladder/anvil/chest are transparent blocks however they brake cactus

@Skylinerw Got it, Thanks!

@Skylinerw So (r=0) is no longer 0.25 block from the executing point?(used to be 0.25 block in 1.8 and snapshots before 16w06a)

Is r=0 really testing "radius = 0" rather than "radius = 0.25"?

/summon ArmorStand ~ ~ ~0.01

and

/execute @e[type=ArmorStand] ~ ~ ~ kill @e[type=Player,r=0]

will not kill the player.

Invalid. Conditional is block state, not NBT data.

The point is that it worked fine in all previous snapshots. Now because of this floor crafting (command block creation) is totally broken.

Not exactly. I have tried to stand at coordinate (1.536,21.00000,0.736) and run command 

/kill @e[r=0]

and I was killed.

/kill @e[r=0]

is still broken, so does 

/execute @a ~ ~ ~ kill @e[r=0,type=!Player]

, so annoying and pls fix! (I think the r=0 is the broken, nothing seems to work with r=0)

Can be confirmed. Same problem.

I think this is intended. See mob in block.

It looks like there's no any NBT tag that states the "condition" for a command block (although I really want it to have).

Are these the features of the newest snapshot? (SEE MINECRAFT WIKI)

Zombies pathfinding works well.

This no longer works.
Use 

/summon Fireball ~ ~ ~ {direction:[0.0d,0.0d,0.0d]}

instead

Thanks for that