Avstar98

I'm not sure if I'm experiencing a different bug or this bug is just more extensive than reported, but in 1.8.1-pre2, the command

/fill -4 64 85 -4 64 95 beacon 0 replace air

returns the error:

[12:53:22] Data tag parsing failed: Invalid tag encountered, expected '{' as first char.

while the command

/fill -4 64 85 -4 64 95 air 0 replace beacon

works fine.

The beacon beam bug is a duplicate of MC-68247. As for the fireworks, you're using blank maps instead of paper.

Are you sure you didn't open your world in 1.7? Downgrading to 1.7 will delete all items in inventories due to a change in how item IDs work.

Any block above a zombie, transparent or not, will prevent a zombie from burning. This is intended behavior.

This is intended. For the time being, names can only be used in commands, and are just an alias for the effect numbers.

An entity can have rotation and motion tags without having an AI.

Actually, it's the Oak Door that has its handle on the wrong side. Unless of course you're placing it next to another Oak Door.

I get this as well in my creative world. It doesn't happen with just bedrock, but rather to any block directly above the void.

This can happen to all entities.

FVBico, your command doesn't work either. The 'minecraft:' isn't required in give commands, but when using testfor, the json must match the entity's NBT data exactly.

Your command is incorrect. You need the full item name in quotes:

/testfor @e {Equipment:[{id:"minecraft:bow"}]}

Were you on singleplayer? Spectators will not keep entities loaded, so going into spectator mode with no other players around causes every hostile/neutral/unnamed mob to despawn, except for Elder Guardians, who do not despawn.

I was unable to reproduce this issue, so there must be more to it. Regardless, you can likely fix it by adding a c=10 argument to the selector.

execute @e[name=FlameBringer,c=10] ~ ~ ~ setblock ~ ~ ~ minecraft:fire 0 keep

This will ensure that 10 entities named FlameBringer execute the command.

This works as intended. The redstone that is attached to the command block on the right is not ever at signal strength 0, but rather is switching between 1 and 14, which is intended behavior. Therefore the command will only be powered once. You can see this for yourself by pressing F3 and looking at the blockStates on the right side of the screen.

Edited for typo.

This does not actually work as intended. The /worldborder max is 30 mil in length, meaning you can only go to 15 mil, 15 mil, much smaller than the actual world. MC-53390 describes the problem better.

It's shaky because the slime blocks make you bounce. Since you didn't fall from a large height, the bounce is very small.

Does this affect all 64x resource packs? If it doesn't it's likely just a problem with the pack.

Tags require you to specify the type of tag they are when using /testfor. For example, the Sleeping tag is a byte, so to testfor someone sleeping you would use {Sleeping:1b}
Just writing {Sleeping:1} defaults to a string tag, which doesn't exist.

Technically the blocks are removed, they just leave a "ghost block" behind. Right clicking the blocks will cause them to disappear, and if you attempt to clone the ghost blocks, it will instead clone the air block that should be there.

The third set of coordinates that you clone to will be the position of the northwest corner of the selection, not the center. This is why it moves in the z direction.