kinsi
Assigned
Reported
MC-11604
The team-scoreboard NOT operand doesnt work right.
Duplicate
MC-11442
Performance issues with item frames
Duplicate
MC-11051
playerKillCount, totalKillCount always assigns the kill to the person, that did first hit a player, even if he has been killed by someone else.
Fixed
MC-6824
[CRASH] 13w02a crashing on startup
Duplicate
MC-6652
Just too much bugs for a title(features comparator)
Invalid
MC-184
(Powered) redstone doesnt update right
Fixed
Comments
@Dinnerbone: couldnt you add one more objective then like "lastHitCount" ? that would be reaally usefull, because in this state its just not use-able by anything
in my tests, it actually always went to the player who did the first hit.
this is really annoying, hope it will get fixed soon.
@Anon Ymus:
i actually did search for it, but couldnt find anything. sorry
@zombie hunter:
"Works As Intended"
also, this gives you trouble, just use this: http://imgur.com/2nCkfPD
@Mustek: starting the launcher as an admin fixed the crash, couldnt you guys just write the stitched images into MC's folder? i dont think that having them in the launcher folder is good 😃
yes, in 1.4.5 prerelease the bug is still there
if you update the blocks(place a block next to it) or relog, the so called phantom blocks should disappear.
Though this particular bug is fixed in 1.6.2, it still gives the kill to the person that did the most damage, not to the last hitter.
i would suggest adding something like "TotalLastHitCount" or something like that, because in the way it is currently, its not that useful