Jit-Yu Wang
- mmis1000
- mmis1000
- Asia/Shanghai
- Yes
- No
MC-34912
What I expected to happen was...:
I though
/setblock -2 64 12 1
will place block at -1.x 64.x 12.x
What actually happened was...:
it place block at -0.x 64 12 1
in short, -1 and 0 place block at the same place
What I expected to happen was...:
I though
/setblock -2 64 12 1
will place block at -1.x 64.x 12.x
What actually happened was...:
it place block at -0.x 64 12 1
in short, -1 and 0 place block at the same place
What I expected to happen was...:
I though
/setblock -2 64 12 1
will place block at -1.x 64.x 12.x
What actually happened was...:
it place block at -0.x 64.x 12.x 1
in short, -1 and 0 place block at the same place
win7 / java7 64 / 6 gb memory
When change the model of a full opaque block (log, wool... etc).
The block still thought itself as a full opaque block.
And hide block after it.
http://i.imgur.com/FgmCFQs.png
May need some options to change this behavior.test texture pack attached
When change the model of a full opaque block (log, wool... etc).
The block still thought itself as a full opaque block.
And hide block after it.
http://i.imgur.com/FgmCFQs.png
May need some options to change this behavior.test
texture pack attachedWhen change the model of a full opaque block (log, wool... etc).
The block still thought itself as a full opaque block.
And hide block after it.
http://i.imgur.com/FgmCFQs.png
May need some options to change this behavior.test resource pack attached
The arrow ignored the rotation parameter of tp command completely
for example
after you run the following command
/summon miencraft:arrow ~ ~ ~ /execute as @e[type=minecraft:arrow] at @s run tp @s ~ ~ ~ ~45 ~The arrow is not going to rotate by 45 degree
It instead just face the
samedirectionThe arrow ignored the rotation parameter of tp command completely
for example
after you run the following command
/summon miencraft:arrow ~ ~ ~ /execute as @e[type=minecraft:arrow] at @s run tp @s ~ ~ ~ ~45 ~The arrow is not going to rotate by 45 degree
It instead just face the original direction
The arrow ignored the rotation parameter of tp command completely
for example
after you run the following command
/summon miencraft:arrow ~ ~ ~ /execute as @e[type=minecraft:arrow] at @s run tp @s ~ ~ ~ ~45 ~The arrow is not going to rotate by 45 degree
It instead just face the original direction
The arrow ignored the rotation parameter of tp command completely
for example
after you run the following command
/summon minecraft:arrow ~ ~ ~ {NoGravity: 1} /execute as @e[type=minecraft:arrow] at @s run tp @s ~ ~ ~ ~45 ~The arrow is not going to rotate by 45 degree
It instead just face the original direction
I though this happens since 1.5.x
It is not only happen in snapshot.
mc1.5.x is super lag than mc1.4.x
"textureFacing": "north"
use this tag to spacify what texture it should show
the "north" here means use the north side texture of the block at it's native position(ex: log without rotation)
"rotation": 90,
and this tag to set rotation of texture
[90] means rotate the texture by 90 degree
and all they work perfect for me
http://i.imgur.com/aAKDJ7f.png
block model of 14w11b use a different format from old snapshot.
be sure you are using the latest format
and this one works
http://i.imgur.com/aAKDJ7f.png
https://mega.co.nz/#!PNF3kRBb!GYAr2ELUKtRov1U74yfCpjwNuFMAhctnQLd9oo-Skyw
14w11b only
Implments in this way makes model useless,
since most of blocks in mc are full opaque.
even we make new model bigger than original.
it will still not work.
since the mc clip the face by direction.
the face exposed outside will still be clipped.
And
bug report is
a feature didn't work as it intends to, though the doc didn't say we can't do that.
feature request is
a feature tends to work in this way, but we want to change it.
as mojang didn't say that limit.
I think it is a bug.
It's actually created by blocks.
Just with some rotating
I believe that the direction is not changed server side, or at least not count into the direction of directional tp at all.
If you intead use ^ directional tp to move the arrow.
In the next directional tp, the arrow is still go straight just like it displayed