MC-119435Despite the fact that the mode of the structure block is not metadata, it may behave that way.
Despite the fact that the mode of the structure block is not metadata, it was rendered as if it had a mode change if it was given to the enderman using the following command.
/summon enderman ~ ~1 ~
{carried:255,carriedData:0}/summon enderman ~ ~1 ~
{carried:255,carriedData:1}/summon enderman ~ ~1 ~
{carried:255,carriedData:2}/summon enderman ~ ~1 ~
{carried:255,carriedData:3}Also, after using the /testforblock command after changing the mode, the data value corresponding to the mode was output like 1.9.
Are these bugs?
Environment
Windows8.1
Created Issue:
Despite the fact that the mode of the structure block is not metadata, it may behave that way.
Despite the fact that the mode of the structure block is not metadata, it was rendered as if it had a mode change if it was given to the enderman using the following command.
/summon enderman ~ ~1 ~
{carried:255,carriedData:0}/summon enderman ~ ~1 ~
{carried:255,carriedData:1}/summon enderman ~ ~1 ~
{carried:255,carriedData:2}/summon enderman ~ ~1 ~
{carried:255,carriedData:3}Also, after using the /testforblock command after changing the mode, the data value corresponding to the mode was output like 1.9.
Are these bugs?
Environment
Windows8.1
Despite the fact that the mode of the structure block is not metadata, it was rendered as if it had a mode change if it was given to the enderman using the following command.
/summon enderman ~ ~1 ~
{carried:255,carriedData:0}/summon enderman ~ ~1 ~
{carried:255,carriedData:1}/summon enderman ~ ~1 ~
{carried:255,carriedData:2}/summon enderman ~ ~1 ~
{carried:255,carriedData:3}Also, after using the /testforblock command after changing the mode, the data value corresponding to the mode was output like 1.9.
Are these bugs?
- Despite the fact that the mode of the structure block is not metadata, it was rendered as if it had a mode change if it was given to the enderman using the following command.
/summon enderman ~ ~1 ~
{carried:255,carriedData:0}/summon enderman ~ ~1 ~
{carried:255,carriedData:1}/summon enderman ~ ~1 ~
{carried:255,carriedData:2}/summon enderman ~ ~1 ~
{carried:255,carriedData:3}Also, after using the /testforblock command after changing the mode, the data value corresponding to the mode was output like 1.9.
Are these bugs?
- Despite the fact that the mode of the structure block is not metadata, it was rendered as if it had a mode change if it was given to the enderman using the following command.
/summon enderman ~ ~1 ~
{carried:255,carriedData:0}/summon enderman ~ ~1 ~
{carried:255,carriedData:1}/summon enderman ~ ~1 ~
{carried:255,carriedData:2}/summon enderman ~ ~1 ~
{carried:255,carriedData:3}Also, after using the /testforblock command after changing the mode, the data value corresponding to the mode was output like 1.9.
Are these bugs?
Despite the fact that the mode of the structure block is not metadata, it was rendered as if it had a mode change if it was given to the enderman using the following command.
/summon enderman ~ ~1 ~
{carried:255,carriedData:0}/summon enderman ~ ~1 ~
{carried:255,carriedData:1}/summon enderman ~ ~1 ~
{carried:255,carriedData:2}/summon enderman ~ ~1 ~
{carried:255,carriedData:3}Also, after using the /testforblock command after changing the mode, the data value corresponding to the mode was output like 1.9.
Are these bugs?
Item metadata != block meta data.
The enderman carrier a block, not an item.
Uh…?
What do you mean?