giving an Item Entity a specific scoreboard number was the only way of locating and manipulating the item entity, now it doesnt work anymore in 1.8.8
wich is a big downfall for any custom map that requires /entitydata at a specific item..
my command block system didnt work and i folowed the problem down to its core.
the commands used:
This one makes shure that a specific item gets a scoreboard DropSwap of 16, as direct Execute at & testfor & entitydata doesnt work on item entities that include NBT:
/scoreboard players set @e[type=Item] DropSwap 16 {Item:{Damage:0s,id:"minecraft:porkchop"}}this one makes shure that all items that have a scoreboard of 16 turn into a different item entity, as soon as my HeatBlade Scoreboard is 1:
execute @a[score_HeatBlade_min=1] ~ ~ ~ entitydata @e[r=5,score_DropSwap_min=16,score_DropSwap=16] {Item:{Damage:0s,id:"minecraft:cooked_porkchop",tag:{display:{Name:"cooked_porkchop"}}}}this command resets the HeatBlade scoreboard back to 0:
execute @a[score_HeatBlade_min=1] ~ ~ ~ execute @e[type=Item,score_DropSwap_min=16,score_DropSwap=16] ~ ~ ~ scoreboard players set @a HeatBlade 0What i expected:
the raw porkchop turns into a cooked version as soon as i swing my blade at the pigs and kill them.
What happened instead:
the items did not change at all
Steps to reproduce:
create a scoreboard that is called HeatBlade as Stat.UseItem.minecraft:Iron_Sword
then crate the famous superfast command block clock by sethbling.
make shure you put all 3 of the commands above into a command block and place them right next to the redstone blocks of the superfast clock, so that all 3 get powered 20 times in a second. swing at a pig with an iron sword to kill them and wait untill the raw meat turns cooked.
My Conclusion:
it worked before 1.8.7, i suppose that the third command doesnt care about how much scoreboard the item entity has so that he skips it and turns My HeatBlade scoreboard back to 0 a bit too fast. i found that out by changing the scoreboard output to something different than 16, but it still choose to change the pork to a cooked version, also further testing revealed that only the meat of the first pigs get changed, all the other raw pork stays how it is.
meaning that the items dont have enough time to turn, because the 3rd command does only care if there is any item on the floor.
Comments 6
Works fine for me. I might recommend changing the third command to
execute @e[type=Item,score_DropSwap_min=16,score_DropSwap=16] ~ ~ ~ scoreboard players set @a[score_HeatBlade_min=1] HeatBlade 0and adding another one:
scoreboard players set @e[type=Item,score_DropSwap_min=16,score_DropSwap=16] DropSwap 0Further testing with the old system revealed that only the first porkchops turn into cooked porkchops, as soon as i contionue slaughtering more pigs, the raw porks stay untouched.
also, the command block timing is overly sensible depending on where it gets placed. it realy depends wether its placed next to the fast clock directly, or allong a line of redstonewire that is connected to the fastclock, the outcome can even varry depending on HOW you place the wire, and in which direction (N,E,S,W).
i ended up placing the command blocks in the order above allong a redstone wire that is connected to the fastclock directly, so that the 3rd command gets executed as 3rd and not earlier. i seem to have fixed the problem myself. it involved a lot of placing the command block all over the place with different outcome tho.
its helpful to tell others to keep this in mind when they do such things themselves.
hope the over sensible command block timing gets solved correctly in the future.
@Anon Ymus
i did use both my variants of the commands and yours, it seems to do the same outcome, but the last command of yours however creates one more problem:
that the third command doesnt have enought time to turn the HeatBleade scoreboard back to 0, as the items dont have the scoreboard 16 for long enough, results into the HeatBlade scoreboard just climbing up every hit with the iron sword.
the way i did it (above) seems to be the solution.
Well, obviously, it depends on the order in which the commands are fired if they all get powered in the same tick. You can identify the order in which they are powered by putting in commands like /say a and seeing what order they appear in chat.
Please provide the exact command you've used and the exact error message (if any)