Alexander

ok

So they have the same effect as normal ones?

My game cheaps kicking me out of the game

I’m having the same issue

[System] [CHAT] Invalid chat component: Use JsonReader.setStrictness(Strictness.LENIENT) to accept malformed JSON at line 1 column 1 path $\nSee https://github.com/google/gson/blob/main/Troubleshooting.md#malformed-json

From log

Affects 1.19.4 and 23w17a

Sadly, it works even in a single-player creative mode. This is what is possible in a

/gamerule doDaylightCycle false & /time set midnight

world within just 7 hours of afk:

So I fixed it using a mod. Turns out, signs are not affected by this bug at all. I am removing all attachments with signs which I can remove.

To fix this, in Mojang's mappings, I upgraded com/mojang/blaze3d/font/TrueTypeGlyphProvider$Glyph#upload from 1-channel image (NativeImage$Format#LUMINANCE) to 4-channel image (NativeImage$Format#RGBA). I moved the luminance channel to alpha channel and set all RGB values to 255 so the whole glyph's image is white. Also I changed TrueTypeGlyphProvider$Glyph#isColored to return true. I know there is a better way to fix it, but this works for me for now.

@violine1101

In short term, MC-161933 is how glyphs with transparent pixels blend with sign model. Transparent pixels near edges of TTF glyphs of some fonts, which created by anti-aliasing, or custom transparent symbols are both rendered in same render pass with sign, so that transparent font pixels replace existing sign pixels, so you can see through signs whats behind them. (Also applies to sac1's screenshot)

This issue however, isn't about how font transparency is handled at runtime. This issue is about Minecraft TTF font's resource reload stage, where it pre-renders all needed glyphs to a texture (where glyphs are rasterized and anti-aliased).

For text coloring reasons, font glyphs are usually rendered in white color, which minecraft does. But what also minecraft does is rasterizing those glyphs on black background (glyph dump attached). This way, the more transparent pixel is, the more black it is. This is a bug and transparent pixels should have not only transparency mask, but also should be rendered on transparent background.

Also, Regular OpenGL's blend functions aren't enough to remove this background the right way. This is why issue name says "anti-aliased", not "rendered".

@sac1 You are all about another bug, MC-161933. Your attached screenshot is not for this issue either. Also my game is not crashing on 1.16.5 when loading the pack.

This is false. My reasoning behind this is that if you have been playing minecraft when 4 J studios was the original of minecraft console edition there is a button to go to old minecraft which contains the option to play minigames and get the achievements. What I think Microsoft should do is make it so that even if your one of the newer players you can go back and play old minecraft. Including minigames. If you have the button it is located under store in the main menu and named as "Editions".

This is not a duplicate problem, this is a completely different problem, because the skin creator works great, but the installation of a custom skin does not work, and I do not understand why you think that it is a duplicate if I noted that it started with version 1.16.220, because everything worked fine on version 1.16.210.05!

Ah for me it wasn’t TNT i don’t think. I launched it with TNT to no effect. I cleared the entities in the world and no TNT was in the list. However there had been pillager raids with only 1/2 showing up the last few days and i believe this was a glitch of the pillagers spawning in untextured with no AI. And since clearing the entity list it has been fine with pillager raids acting properly

Can someone help me?

Ah yes the classic its a feature, not a bug