I was experimenting with command blocks. I was trying to create bows that do not damage anything. I knew you could change the arrow's damage value with the {damage:} data tag. I set up a redstone clock which activated the command 20 times per second and I set the damage value of the arrow to -10 by attaching a command block with the following command: /entitydata @e[type=Arrow] {damage:-10}. When I shot an arrow, it crashed my game.It didn't crash my world or delete any of my progress luckily though. I think I know why it crashed my game but I'm not completely sure. I think it is because the {damage:} tag couldn't handle negative values and detected it as an valid command although it could crash my game. It detected it as valid because of a bug. The command feed back was valid and wasn't an error, otherwise is would have detected it as invalid and would have blocked the command from running.
I was experimenting with command blocks. I was trying to create bows that do not damage anything. I knew you could change the arrow's damage value with the {damage:} data tag. I set up a redstone clock which activated the command 20 times per second and I set the damage value of the arrow to -10 by attaching a command block with the following command: /entitydata @e[type=Arrow] {damage:-10}. When I shot an arrow, it crashed my game.It didn't crash my world or delete any of my progress luckily though. I think I know why it crashed my game but I'm not completely sure. I think it is because the {damage:} tag couldn't handle negative values and detected it as an valid command although it could crash my game. It detected it as valid because of a bug. The command feed back was valid and wasn't an error, otherwise is would have detected it as invalid and would have blocked the command from running.