[1.46][SSP] turtle.compare() fails with Leaf block/items

ComputerCraft Version Information: 1.46 Computer Craft, Minecraft 1.4.2, (mod via FTB)

Description of Bug:
Using the turtle.compare() function returns false when comparing Spruce Leaves (NEI 18:1) against leaves attached to a tree grown with bonemeal. I also tested Oak Leaves, but stopped after that.

Steps to Reproduce Bug:
1. Place spruce sapling.
2. Grow spruce sapling.
3. Place turtle facing the leaves.
4. Acquire "Spruce Leaves" item via shears or NEI.
5. Put a "Spruce Leaves" item in the 1st inventory slot of turtle.
6. Execute command "lua".
7. Execute command "turtle.compare()".

Expected Result: true
Observed Result: false

Compare gets the items that would be returned throught he "pick block" function in creative if I recall correctly. So when you do that, you would get a sapling. I might be wrong, but it might be what you are having a trouble with.

Cranium, on 17 November 2012 - 05:39 AM said:

Compare gets the items that would be returned throught he "pick block" function in creative if I recall correctly. So when you do that, you would get a sapling. I might be wrong, but it might be what you are having a trouble with.

I tried the same steps but comparing against the sapling item, still results in false. My end goal is to get a "true" when using compare() against leaf blocks.

Cranium, on 17 November 2012 - 05:39 AM said:

Compare gets the items that would be returned throught he "pick block" function in creative if I recall correctly. So when you do that, you would get a sapling. I might be wrong, but it might be what you are having a trouble with.

Not yet. It will in future though which will fix the above issue.

Thanks Cloudy. I was using the same app I use for mining and it started just eating leaves instead of ignoring them. I was all wtf. Glad to know I'm not crazy. I'm really enjoying ComputerCraft!

Are you still planning to fix this bug?
I am using CC v1.5.3 and its still not able to compare leaves.

You're not on the latest version, so you should be trying to reproduce bugs in the latest version before you post them. Yes, it is still a planned fix. No, it hasn't been fixed yet.