very slight but useful change to turtle.compare()

as is compare and compareTo checks if both the ID and meta data is the same as the item its holding, but it cant detect if its the same type of block but just slightly different.

so i propose a change to the command to include a optional boolean value that is normally set to true , but if the user wants they can set it to false making it compare only the id and not the meta data. this way items like wool , logs , saplings , and dyes will be detected as the same item type even if one is blue and the other is red.

this shouldn't be over powered but would be a rather nice and fairly simple change. but just to be clear i am NOT asking for the over used "gimme the items id" :P/>

I believe that they were working on altering compare to use the "pick block" value, so that it wouldn't be as badly affected by metadata and such (it would also be highly valuable in that it should allow comparison of ores to their resource drops). I'm not sure how much progress they've made on that.

I don't like the idea of just comparing against ID. Once we improve compare most issues should go away.

How does compare handle damage bars? (currently or after the planned changes)

immibis, on 28 December 2012 - 12:21 PM said:

How does compare handle damage bars? (currently or after the planned changes)

Why would compare care about damage bars? These are blocks in the world

compareTo() isn't blocks in the world, necessarily. ;)/>

Edit: Though, you are absolutely right, in that compare() is just blocks in the world.

some blocks in the world have damage bars ( kinda ) look at factorization and its batteries

Cloudy, on 28 December 2012 - 01:58 PM said:

immibis, on 28 December 2012 - 12:21 PM said:

How does compare handle damage bars? (currently or after the planned changes)

Why would compare care about damage bars? These are blocks in the world

Yep, dumb question. I did mean compare btw, not compareTo.