Minecraft Forums

Quote from Wayuki

The best solution IMHO would be to add a mask texture, where you can add parts not to be affected by the dye. This would at least allow for different colored trims, buckles, etc.
(snip)

Yup, but it still creates an awful mess because of the horrid hues they hardcode. I don't know what they were thinking.

...whoa, scary thought - I hope they don't change wool to be that way for their convenience. That would be monstrous.

update it to 12w34a

Hey there. Getting this crash with the new patcher version (2.4.2)
Anybody know how to fix it?

org.lwjgl.LWJGLException: Could not get the JAWT interface
at org.lwjgl.opengl.AWTSurfaceLock.lockAndInitHandle(Native Method)
at org.lwjgl.opengl.AWTSurfaceLock.access$100(AWTSurfaceLock.java:49)
at org.lwjgl.opengl.AWTSurfaceLock$1.run(AWTSurfaceLock.java:89)
at java.security.AccessController.doPrivileged(Native Method)
at org.lwjgl.opengl.AWTSurfaceLock.privilegedLockAndInitHandle(AWTSurfaceLock.java:86)
at org.lwjgl.opengl.AWTSurfaceLock.lockAndGetHandle(AWTSurfaceLock.java:64)
at org.lwjgl.opengl.MacOSXCanvasPeerInfo.initHandle(MacOSXCanvasPeerInfo.java:53)
at org.lwjgl.opengl.MacOSXDisplayPeerInfo.doLockAndInitHandle(MacOSXDisplayPeerInfo.java:56)
at org.lwjgl.opengl.PeerInfo.lockAndGetHandle(PeerInfo.java:85)
at org.lwjgl.opengl.MacOSXContextImplementation.create(MacOSXContextImplementation.java:47)
at org.lwjgl.opengl.Context.<init>(Context.java:120)
at org.lwjgl.opengl.Display.create(Display.java:858)
at org.lwjgl.opengl.Display.create(Display.java:784)
at org.lwjgl.opengl.Display.create(Display.java:765)
at net.minecraft.client.Minecraft.a(SourceFile:233)
at net.minecraft.client.Minecraft.run(SourceFile:516)
at java.lang.Thread.run(Thread.java:722)
--- END ERROR REPORT 142dbe5f ----------

Like I said earlier, I'd suggest putting out a option to change the default color of the armor before working on the millions of color combinations.

Quote from Balduran

Yup, but it still creates an awful mess because of the horrid hues they hardcode. I don't know what they were thinking.

...whoa, scary thought - I hope they don't change wool to be that way for their convenience. That would be monstrous.

I'm not happy about it either. One workaround for texture artists is to tint and hueshift the grayscale texture instead of having it actually grayscale. It adds some depth the the colors. I've actually already done that in my texture pack to anything with automatic recoloring.

I'm traveling this weekend, so I don't have a lot of free time, but I was able to make a quick compatibility update for the latest snapshot. Links are in the OP. /title/mojang.png graphic is fixed also.

You can customize the dye colors in color.properties. I suspect that this will affect the armor dyes, but haven't tested it myself.

So I don't know where to ask this, but I figured here would work well enough. Would it be possible to add a glow overlay to textures like how the endermen/dragon, and spiders have their _eyes? Or if someone could point me toward a mod that does as such...?

Does anyone know where I could get a version of MCPatcher compatible with Alpha 1.0.17_04?

12w34b just scans as 1.3.2 and i cant play.

Quote from Balduran

I'm continuously shocked as to why everyone keeps tossing that number around... Mojang were just bragging as they always do (Or using hyperbole to end the discussion. I wouldn't be surprised)
The actual number would be 96 textures, and that's it. It's still an awful lot of work, but it's doable.

So unless i'm counting this the wrong way, there is a total of 16 dyes, and each armor texture uses 2 files, plus 4 item icons, therefore:
(16x4)+(16x2)=96 separate textures


Exactly. If they weren't cutting corners, they wouldn't add such a lazy dying method in the first place. We can safely assume that '16 million' is just a random number, just like having 2,5k potion recipes.

It would be good if they made a separate wool armor that could be dyed, instead of using leather... I made a suggestion on reddit, don't know if anyone will read it.

Anyway, I have an idea. Code it so that undyed armor looks like standard leathers. But when it is dyed, change the texture to the shirt that is the 12w34a armor.

Also, if you wanted to customize the armor colors, you could make it work the same way as the biome color image. I'm not sure how you would get it to work in 3D however.

Quote from _zombiehunter

The actual MCPatcher version should theoretically work with old MC versions too. If not, github is your friend:
https://github.com/p...tcher/downloads
I'm sure you'll find a MCPatcher version working with "MC Alpha 1.0.17_04" here ...

I've actually looked through the github area already and no luck. They're ordered by version number, but not MC version number.

Quote from Kahr

I'm traveling this weekend, so I don't have a lot of free time, but I was able to make a quick compatibility update for the latest snapshot. Links are in the OP. /title/mojang.png graphic is fixed also.

You can customize the dye colors in color.properties. I suspect that this will affect the armor dyes, but haven't tested it myself.

Unfortunately, it doesn't.

Just found out there are 16777215 combinations for armor color. I doubt dyed colors will be supported, save for default armor color.

I'll just wait until an official Mojang build before getting this, with all the bugs and what-not. 1.3.2 it is.

I have the Norton security program, and it is saying the download is unsafe... I have used these downloads in the past and everything is fine, can someone please help me figure this out?

what is the night vision file called?

Alright. Just downloaded it for Mac from Github. What do I do now?

2.4.2_01 triggers Norton as well with the same (fake) reputation alert. Supposedly, filling out this form and saying you're the developer will quell future FPs from Norton. Would you be willing to do so?