1Darco1
Assigned
Reported
Comments
Standing in the Fence
Fully able to reproduce 😉
The game seems to see the Fence as a 1m tall block --> You can place it under yourself, while jumping --> It realizes, that it is normally 1.5m tall --> Because you can not stand on a fence after jumping (You can´t jump 1.5m up), the Game will let you stand IN the Fence.
See screenshot.
That is a feature of TheEnd. Every Time an entity (Player, Mob, Dropped Item, FallingSand) travels through the EndPortal, the EndSpawn (obsidian platform) is reloaded and all Blocks on (and under) the Platform are destroyed. The feature was implemented to make sure, that nobody can e.g. suffocate when he wants to go to the End.
I---> This is not a bug and can be closed.
Unable to Reproduce.
I made an area FULL with tall grass and bushes (see screenshot). They started burning anyway.
I also spawned Skeletons/Zombies between 2 Tallgrass and they´re all burning and not hiding. Some of them even ran away from the Tallgrass 😃
Did you program another code for Minecraft, or what? 😛 So, however I think that the Skeleton which ran into your Tallgrass, was random.
CU
EDIT: Not necessary to upload my Screens anymore. Kumasasa did it same way.
Tried it and again the Disconnect from the Server-Side...
I´ve deleted the scoreboard.dat and all player.dat/player.json. I´ll ask my friend later to join the server and klick the Redstone Button. I think I just mixed up EVERYTHING in my world... You can close this 😉
Okay guys,
this is kinda weird... I started a new world and build only these CommandBlocks.
Same Server and everything was fine. Maybe I mixed the Scoreboard in my old world up, that it didn´t work. I´ll now retry the thing in my World with deleting all the Scoreboard-Data...
This is no bug I think, just a Issue appearing through my mistakes :o
I´ll give a last Comment what happened after deleting the Scoreboard-Data
CU
So this is my crash report.
I am busy until this evening so i will check it again and force the crash then.
CU
Sure, but I just want to point out, that the /tellraw Command worked fine until I added the /testfor Clock. You have in a Sec in the description.
Did it! 🙂
I can confirm this bug but I also found a solution:
you can use: '/testforblock x y z minecraft:piston_head'.
'36' or 'minecraft:piston_extension' gives me the Error you have, too.
WOOP! Fully able to reproduce (MAC OS X 10.8 / Snapshot 13w37b).
Didn´t realized that yet 🙂
See description, I agree.