This one is difficult to reproduce and difficult to pinpoint what exactly causes the error, but I have a few observations.
When using commands that analyze the tags of an Arrow entity e.g.
/scoreboard players tag @e[type=Arrow] add Meh {inGround:1b}, if there are too many Arrows, Minecraft returns the following: "An unknown error occurred while attempting to perform this command". Such an observation can also be made with commands such as
/entitydata @e[type=Arrow] {...}In addition to that, even if you only select a single Arrow entity, the error still occurs. e.g.
/entitydata @e[type=Arrow,c=1] {...}This only occurs if you have very many Arrow entities present (not extremely sure what the cut-off point is, but I reckon about 200).
Has also been tested with cows and zombies, does not happen. Not extremely sure about other entities. (Happens with Spectral Arrows)
STEPS TO REPRODUCE:
Create a world (or just open one up)
Shoot an arrow in the floor and run this command:
/entitydata @e[type=Arrow] {}, and you should see: "The data tag did not change: {...}"
Place down a repeating command block and input the following command: /summon Arrow ~ ~20 ~. Power the command block using any form of redstone for about 10 seconds and allow the arrows to fall.
Run this command:
/entitydata @e[type=Arrow] {}, and you will see: "An unknown error occurred while attempting to perform this command"
This command will also trigger the error:
/entitydata @e[type=Arrow,c=1] {}.
You also can't target them with /entitydata (/entitydata@e[type=Arrow] {} gives an error), but you can target them in /kill
See duplicate report (MC-93374)
Linked issues
is duplicated by 3
Comments 5
the title is very misleading, it doesn't matter how many there are, the only thing that matters is that they are /summon-ed
I request the title and description are updated accordingly
@@unknown: Updated title based on duplicate report, please suggest changes to title and description if there still is room for improvement.
You also can't target them with /entitydata (/entitydata@e[type=Arrow] {} gives an error), but you can target them in /kill
See my duplicate report (MC-93374)
Confirmed, but it doesn't matter how many arrows there were. Any plain arrows or spectral arrows spawned via commands will throw that error. As well, the chunk the arrow is in will not be saved and a "Couldn't process command" error is added into the logger.
Seems to be caused by the lack of a "pickup" tag. If applying it manually, regardless of value given, the summoned arrow functions normally. If summoned without that tag, the issues described in the report occurs. Checking the source, it looks like it may be caused by a null value as the default for the pickup type.
As a side-note, if the "player" tag is specified, it's used as a fallback for a missing "pickup" tag and the error no longer occurs. That tag should not be used though since that fallback behavior is akin to deprecation.