MC-66118Weird /entitydata behaviour when used with dx, dy, dz
When /entitydata is used with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}
on a row of 50 wood items results in this:
(This is the only item that was changed to stone). For the items that weren't changed, it outputs "The data tag did not change: [...] id:"minecraft:stone" [...]", even though they're still displayed and handled as wood items.
Environment
OS: Windows 8.1 64bit
Java: Version 7 Update 65 (Build 1.7.0_65-b20)
Attachments1
Created Issue:
Weird /entitydata behaviour when used with dx,dy,dz
When using /entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e\[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
Environment
OS: Windows 8.1 64bit
Java: Version 7 Update 65 (Build 1.7.0_65-b20)
Attachments1
When using /entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e\[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
When using /entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e\[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
When using /entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e\[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
For the items that weren't changed, it outputs "The data tag did not change: [...] id:"minecraft:stone" [...]", even though they're still displayed and handled as wood items.When using /entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e\[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
For the items that weren't changed, it outputs "The data tag did not change: [...] id:"minecraft:stone" [...]", even though they're still displayed and handled as wood items.
When using /entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e\[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
For the items that weren't changed, it outputs "The data tag did not change: [...] id:"minecraft:stone" [...]", even though they're still displayed and handled as wood items.When using /entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e\[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
For the items that weren't changed, it outputs "The data tag did not change: [...] id:"minecraft:stone" [...]", even though they're still displayed and handled as wood items.
When using /entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e\[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
For the items that weren't changed, it outputs "The data tag did not change: [...] id:"minecraft:stone" [...]", even though they're still displayed and handled as wood items.
When using /entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
(This is the only item that was changed to stone). For the items that weren't changed, it outputs "The data tag did not change: [...] id:"minecraft:stone" [...]", even though they're still displayed and handled as wood items.
Weird /entitydata behaviour when used with dx, dy, dz
When
using/entitydata with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.Example: Running
/entitydata @e[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
(This is the only item that was changed to stone). For the items that weren't changed, it outputs "The data tag did not change: [...] id:"minecraft:stone" [...]", even though they're still displayed and handled as wood items.When /entitydata is used with an entity selector that contains dx, dy and/or dz, it seems to only change the data of one random entity in the specified range.
Example: Running
/entitydata @e[0,11,0,dx=49,dy=0,dz=0] {Item:{id:"minecraft:stone"}}on a row of 50 wood items results in this:
(This is the only item that was changed to stone). For the items that weren't changed, it outputs "The data tag did not change: [...] id:"minecraft:stone" [...]", even though they're still displayed and handled as wood items.
Please do not mark unreleased versions (anything starting with "Future Version") as affected. You don't know if it will be a problem in the future.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.