MC-8429Font textures in texturepacks don't work
After placing your font textures (default.png, alternate.png) inside the font-folder of your texturepack, the game still uses the default texture files in minecraft.jar. This happens with every texture resolution (even with native res textures).
This is not a feature suggestion, it's a texture-related issue that needs to be fixed like all others too !!!
It's the same as the game would always use for e.g. the default particle textures instead the textures placed in your texturepack, the font textures have the same priority !
Linked Issues
is duplicated by1
Created Issue:
Font textures in texturepacks don't work
After placing your font textures (default.png, alternate.png) inside the font-folder of your texturepack, the game still uses the default texture files in minecraft.jar. This happens with every texture resolution (even with native res textures).
This is not a feature suggestion, it's an texture-related issue that needs to be fixed like all others too !!!
It's the same as the game would always use for e.g. the default particle textures instead the textures placed in your texturepack, the font textures have the same priority !
After placing your font textures (default.png, alternate.png) inside the font-folder of your texturepack, the game still uses the default texture files in minecraft.jar. This happens with every texture resolution (even with native res textures).
This is not a feature suggestion, it's antexture-related issue that needs to be fixed like all others too !!!
It's the same as the game would always use for e.g. the default particle textures instead the textures placed in your texturepack, the font textures have the same priority !
duplicates
MC-7064
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
Duplicate of: [MC-7064] - Please use the search function to see if your bug has already been submitted.
Currently over 45% of tickets are being closed as duplicate.
This is not a duplicate, this is just a more general report of this issue because it's not limited to HD textures as mentioned in MC-7064!
Why are you always marking this as "resolved" ???
This is an issue that needs to be fixed !!!
Maybe you should read the content of an issue report first before closing it and keep the most accurate ones open!
And only if you don't work with textures, this doesn't mean you can arbitrarily close every texture-related issue just because you're not interested in it (or whatever the reason is) ...
zombie hunter, you should be able to adjust the subject and description of that earlier issue to match better the situation (i.e. that it does not only affect HD textures) (unless being resolved locks them from changes, that would be a big "doh!"), no need to open another issue about it. However, considering that the old one was already resolved (which is practically the same as closed in this JIRA), I can understand opening a new one, it seems to be the only way to get a decent chance of attention to past issues.
In the old issue, it might help if someone could find the source of official words about promising support for fonts from texture files, too, after these texture changes, and add link to such in the comments.
Unfortunately, there are no official words about it, Mojang never cared about the font textures. It would be an easy fix to activate them for texturepacks though, and now would be a good time to do it along with all the other texture-related changes in MC1.5. Mojang just needs to be made aware of this issue and this issue tracker is the intended way to do this, or not?
So why the hell is this still marked as "resolved"? It's an issue that needs to be fixed, not a feature suggestion.
Unless you can provide evidence that this should be in the game (confirmed by devs), this is not an issue but a feature request. If everyone is going to post their annoyances, or think something should be in the game, this place would be unmanageable.
It really doesn't matter whether an issue is classified as a bug or a feature request. What matters is that you make a compelling argument for the change, and the developers have a chance to see and consider it. So go with the flow. If an issue you care about is rejected here, don't fight it – post on the suggestions forum or subreddit.
Aaaaaaand fixed as of 13w09a. Even HD fonts work.