Simon Woodington

Tested with 128x and 256x resolution packs. Errors not reproducable. Probably a case of human error. Chances are I shouldn't have posted this bug whilst under the influence of the flu.

Unless anyone else can confirm/reproduce, this bug can be closed.

Thanks for your time.

Absolutely. It can be reproduced with the currently released version of ACME Pack and ACME Christmas Pack:

http://www.mediafire.com/download/eba4xn644z324an/ACME_Pack_64x_MC17.zip

http://www.mediafire.com/download/toamzll5tlhbzd1/ACME_Christmas_Pack_256x_MC17.zip

Reproduction is just a matter of loading the ACME Christmas Pack over the ACME Pack.

I wasn't at all sarcastic. I don't understand why this slipped through when it was such a big feature.

That being said it's not actually part of the bug, so remove it if you will, but I stand by my statement. Professional standards are. Period.

Which is brilliant except for the fact that Minecraft's colormap functionality is MIA, putting MCPatcher on notice.

It's definitely not a mistake. We get it; Mojang is trying to add color to an otherwise "drab" object, but was it necessary to do it so lazily?

Something to consider: Why not just change this to bamboo and add real sugar canes?

Let the bamboo be influened by biome color and let texture devs play with what is now sugar cane?

Just a thought.

A demonstration of how the current method of coloring sugar cane affects four different resource packs in snapshot 13w38a.