in versions before 1.8.3 I know that you could make armourstands with custom playerheads just larger than a block. in the newest versions, howerver, custom playerheads do not work, I wouldnt use new versions for command blocks for several other reasons, too, such as rendomized dispensers.
/execute's syntax:
/execute <target> X Y Z <command>
/execute <target> X Y Z detect X Y Z <block> <Damage> <command>
There is no section for dataTags. You must use a command that supports dataTags to apply a label based on NBT data first, such as /scoreboard
, and then target the entity based on that label.
You should also not be using numerical IDs, since they are deprecated in 1.8 NBT data (and unusable in most command syntax) and no longer works at all in 1.9.
Item replacement
Instead of summoning a new item to 'replace' another item, you can use /entitydata to change the ID of the already-existing item.
Prerequisites:
An objective to label the item entity as being a double plant.
/scoreboard objectives add DoublePlant dummy
Clock commands:
The following must be run in numerical order on a clock.
First, assign a score to items that are double plants.
/scoreboard players set @e[type=Item] DoublePlant 1 {Item:{id:"minecraft:double_plant"}}
Change the ID of the item using /entitydata.
/entitydata @e[type=Item,score_DoublePlant_min=1] {Item:{id:"minecraft:log"}}
Reset the score of the item.
/scoreboard players reset @e[type=Item,score_DoublePlant_min=1] DoublePlant
Entity replacement
As per title, if you intend to replace an item entity with a non-item entity, you will need to use /execute like you've done, but with the proper label.
Prerequisites:
An objective to label the item entity as being a double plant.
/scoreboard objectives add DoublePlant dummy
Clock commands:
The following must be run in numerical order on a clock.
First, assign a score to items that are double plants.
/scoreboard players set @e[type=Item] DoublePlant 1 {Item:{id:"minecraft:double_plant"}}
Summon a new entity at double plant items.
/execute @e[type=Item,score_DoublePlant_min=1] ~ ~ ~ summon Creeper
Kill the item entity to prevent constant summoning of creepers (which will also clear its scoreboard.dat record automatically).
/kill @e[type=Item,score_DoublePlant_min=1]
1.9 changes
Instead of using scoreboard objectives, you can use the new "tags" feature to apply a label directly onto the entity. The benefit is a less-bloated scoreboard.dat (since scoreboard.dat is not involved at all) and easier prevention of constant command activation.
Assign a tag to items that are double plants.
/scoreboard players tag @e[type=Item,tag=!DoublePlant] add DoublePlant {Item:{id:"minecraft:double_plant"}}
Change the item's ID using /entitydata while also removing all tags from the item at the same time to prevent constant activation.
/entitydata @e[type=Item,tag=DoublePlant] {Item:{id:"minecraft:log"},Tags:[]}
Best Answer
This is both possible and a late answer.
I don't know too much about it, but I believe you can use
/execute
. This will run the command from the perspective of an entity, so the relative coordinates will be centred on the entity, rather than the source from which the command was run.Something like this should work, replacing the coordinates and removing the brackets:
/execute @p ~ ~ ~ clone (<x1> <y1> <z1>) (<x2> <y2> <z2>) (<x3> <y3> <z3>)
So, for the final set of coordinates (x3,y3 and z3), you can use the
~
to clont relative to the player