Negative Color Crosshair when using resource pack

This happenes in 90% of my resource packs. The crosshair is fine after death but as soon as you pickup or hold an item in your hand it becomes a square.
Resource packs with small pointers had this problem less than those with bigger ones, maybe this info might help.

Broken resource pack.

Remove your resource packs and check if it still happens.

Why is this resource pack related, when it was working in the earlier versions? It DOES work on the default but that's not a solution. They aren't broken, when I have no items on me the crosshair appears normally, but as soon as I have an item on me the square appears.
This has to be reopened.

I've attached an image, that simply explains how this error occurs.

How in the hell this is "invalid". The cursor gets distorted when an item is in the hotbar!

[svajoklis_] is this occurring without a texture pack for you?

It happens only when using a resource pack that has the crosshair changed, so no. But isn't that an issue with resource packs in general then? The .png file is changed ONLY by deleting some pixels (making them completely transparent) and saving it back in the same format. No other GUI elements are distorted. The only distorted element from that .png is the crosshair.

I don't get it why people think resource packs are broken and not the game itself, no files in the gui changed since the previous snapshot as I was compairing the file-changes. Only model files and of cource new textures (but none of them gui related).
Like [svajoklis_] said it happens to those pack which have the icons.png in the gui folder changed. Especially when the crossbow is filling up a large space, small crossbows do not change into a square.
P.S. if this really is a bug caused by an resource pack that is not correct how can we (resource pack makers) fix this problem? Tried couple possibilities but none of them succeeded.

Ok, I have reloaded the game and then removed res-packs from the 'using' list. I loaded them back up and now the crosshair works correctly. Even when using shaders!

Perhaps it was fixed in the b version. EDIT: Just checked it, it was fixed in the 14w25b version.

This is not fixed for me in 14w25b. I've noticed that it only happens when I have exaclty 1 item of a particular kind in my hotbar. So when I have for example 2 cobblestone the crosshair appears normally but when I have 2 cobblestone and ONE diamond the square appears. This definately is a minecraft bug. Please reopen this so devs can actually dig into this issue.

I can confirm this. If you have any stack of more than 1 item then crosshair is normal, if you have only tools and/or stacks of 1 item then crosshair is distorted.

This is still going to stay invalid, as its an issue with the resource pack itself. The creator of the resource pack needs to update it. For now, try to play on the default resource pack, or try to fix it yourself.

Blah you aren't even a mod so it isn't for you to decide whether this issue should be invalid or not. And if you suggest suddenly all resource packs are broken what should resourcepack makers do to fix this? Seems you have some knowledge, since you say that the resource packs need fixing. Unless you have proof that the resource packs are broken and not minecraft don't mislead the mods.

Its not an issue with Minecraft. Its an issue with the resource pack. This report was already resolved as invalid. Not misleading.

Let's just call it a day.

Cannot confirm on default pack.

It was resolved as invalid because you mislead the mods in the first place... Why do you comment on things you do not have any proofs or valid knowledge about? You weren't even able to answer my question about a possible fix of this issue.
One more time, this is a minecraft bug. And to proof more that it is so I've made a copy of the snapshot jar and changed in it only the gui/icons.png. When I was playing in the default texture pack, with no other resource pack enabled the cursor WAS still obscured. This especially is seen in files that have bigger resolutions. When adding a couple pixels to the default crosshair it isn't beeing a square but it hase some weird lines going on.
Try it if you don't believe me and stop talking about matters you have no clue about.

Still cannot confirm. Its you that is changing the icon, which means that you are modifying the default pack. Your "default" pack is also broken.

Sure I was modifying the icon but that's the point of resource packs. I don't know why it is so difficult for you to understand, every attempt of explanation seems to go through you like dust im my PC so I'm not even bothering. I'd rather let a mod with some oil in his head check this out. This bug annoys the hell out of me but more annoying is the fact that it is invalid because of people with no clue how resource packs work telling that they are broken and not the game.

I've gone through about 10 different resource packs all made by different people. Each one of them has the inverse crosshair glitch. When the hotbar is empty the crosshair is COMPLETELY NORMAL as it's meant to be in the resource pack. Placing one item of any type into the hotbar will make the crosshair glitch and become an inverse square. Placing a stack of two or more of any stackable item in the hotbar makes the crosshair revert back to how it SHOULD be in the resource pack. This isn't an issue with the resource pack, it's an issue with the game. Even though it doesn't happen in the default resource pack, it IS an issue with the game because it only triggers due to circumstances not relating to the textures in the resource pack. Even altering the crosshair by one pixel in the default texture will cause this glitch.

You say it's an issue with the resource pack, well then enlighten us on a way to fix said issue. You seem to know how considering your lack of a response to any point brought up about it says you clearly know everything.

Reopened.
It's up to Mojang to decide if bug in Minecraft or broken resource pack since the model format has changed, see MC-56987

Seems a bug with the alpha channel. Try to create a pixel near the default crosshair, then delete it. You will see that the deleted pixel still will appear in the negative.

If that pixel is deleted and still showing then it's no Minecraft bug, but a matter of badly created icons.

You say that Photoshop or other programs create messed up alpha channels? That's weird, especially when it was working and is working in some situations but not when I have 1 block of any kind in my hotbar. This is confusing.
I think it is more like corrupted minecraft reading those alpha channels rather then the opposite.

I was able to "fix" my resource pack by saving the icons.png gui file in an 8 bit format (Using Paint.NET) which fixed the alpha channels.

So it seems that this is indeed a problem with how MC handles the alpha channels now.

My "fix" was using simply black as the alpha channel, seems to work but this definately is an issue for those packs, which use standard alpha channels.

The original icons.png is in 32-bit format.
Aren't we supposed to make resource packs work too? Oh hurr it works on the default, let's call it a day. Oh lol you can't draw a proper crosshair. What a fine attitude!

I extracted the original icons.png, opened it up in photoshop, deleted some pixels off of the image, saved it in place (didn't have to select any settings) and for some reason now it reverts to the original (the pixels I deleted return). I changed some more pixels and it got more distorted (I am using a brush that's (255,255,255). It works when the bar is clear or there are stacks of 2 items, doesn't work when there's only stacks of 1 item and/or tools.

Also have the crosshair issue in snapshot b with my resource pack – only when stuff is in the inventory bar.

people please vote for this issue because it needs to be fixed.

Seems like this is more a texture pack issue than a game issue. Still, really frustrating to always have to fix texture resource packs. Would like to hear a proper fix. Meanwhile I'll continue playing with my texture packs icons.png in the hope of restoring my crosshair and xp bar.

For what is is worth, this bug effects such popular resource packs as: Sixty Gig, Chroma Hills, Sortex Fanver, Good Morning Craft, and Frehdens' Meringued, as well as my own Lithos:Core.

For those who claim this is a case of artists making their pack "wrong", please explain what we did wrong and how to fix it.

I used a pixel style eraser that is at 100% opacity. It made the alpha channel completely clear. And it's my own choice if I want to remove the crosshair, it makes no sense.

Did you even try it yourself or do you just blame everything on the imcompetence of the user?

Ignore him, he does have no idea what he is talking about. My black background fix works but still waiting for any mojanger to comment on this.

A few extra notes:
1) It is not just minecraft:prismarine that has the problem. Other items that have the problem inculde a water bucket, a saddle, gold horse armor, an arrow, a potion, a sword. Examples of items that do not have the problem include leather, white wool, netherack, oak wood, an iron shovel, flint-and-steel.
2) Having an inventory item with the problem in your hotbar is sometimes (see next point) sufficient to show the issue. You don't need it to be selected. Having a "bad" item in your normal inventory doesn't seem to be a problem.
3) The placement in the hotbar matters. It appears the only determining factor is the LAST NON-EMPTY HOTBAR slot. If that is a "good" item, there is no problem, even if "bad" items exist in the hotbar. If the last non-empty hobar item is a "bad" item, you experience the problem. If the hotbar is completely empty, you do not experience the problem.

WORKAROUND UNTIL MOJANG FIXES THE PROBLEM: Put a "good" item such as a shovel in your last hotbar slot.

Dolphin263 the only thing that works for me is having more than one of a block in my inventory. I have tried your method but it didn't work. What items/blocks that wok may differ with resource pack but over all this bug is with Minecraft not with the textures themselves.

So is anyone going to attach or link to a resource pack that exhibits this issue?

Here's one, the cursor is changed to be a little sun thing. The only file changed is the icons.png

https://drive.google.com/file/d/0BxTOjO65cgphb1VvSy1ONEdseEE/edit?usp=sharing

THANK YOU 🙂))))))))

Thanks so much this is one of the most annoying bugs I have ever encountered.

This is NOT fixed yet (as of 14w26a)

Now it works fine until you pick up 1 item, but if you pick up any more it fixes itself...Very odd o.o

For me nothing has changed as of 14w26b, I still have the bug unless I have more than one of an item in any hot bar slot. For instance if I have only one cobblestone in my hot bar I have the bug but if I have a stack of anything whether it be 2 or 64 of that item the bug does not appear.

I am also still having issues in 14w26b...

I also still see the issue in 14w26b. As I said before it seems to be dependent on the item in the right-most non-empty hotbar slot.

Update: Bigman1103 said he noticed that it seemed dependent on the number of items in the hotbar slot. After experimenting a bit more, I see think I can see the pattern. Can people who have the bug see if the following rules determines whether you have the problem?

1) Look at your last non-empty hotbar slot.
2) The problem won't exist if that item has damage.
3) The problem won't exist if that item has a count > 1
4) Otherwise (no damage AND count=1) the problem exists

For example, one arrow=bad. Two arrows=ok. damaged shovel=ok. Pristine shovel=bad.

With the above, I no longer think it is inconsistent on what causes the issue, but I will update if I see any counter examples.

Version 14w26b June 25th. First time I ever seen this bug, not fixed. Edit: also note I'm on a PC windows 7.

If this is still a concern in 14w26c, please update the versions affected.

I confirm I still see the behavior in 14w26c.

Still a bug in 14w27a/b

I still see this issue happening in 14w27b

I too am still having this problem. Not fixed!

@@unknown This issue is solved for "Future Version - 1.8" - read: next upcoming snapshot.

This is fixed for me in the newest snapshot 🙂 Thanks

it has been fixed for me as well.

Thanks for fixing this!!!! (Works for me too in 14w28a)

Fixed, yay!!