Luke W
- Luke18033
- luke18033
- America/Los_Angeles
- Yes
- No
MC-101514
MCPE-15828
MCL-4962
When I shoot a mob with a spectral arrow or give a mob a glowing effect with a command, the game (not the UI) goes black, the mob being shown as a white object in the shape of the mob. I have tested this with and without OptiFine, it happens both ways.
EDIT: The bug changes every time I launch MC. Sometimes it does what is described above, sometimes it does the same but without turnining the screen black and sometimes the effect doesn't do anything at all.
Spectral ArrowGlowing Effect is BrokenGlowing Effect Rendering is Broken
When loading most of my worlds, they load fine and I can play them, but when loading my superflat world, the game crashes when I try to move or look around. I have previously used mods in this world, but I had loaded it in 0.14 after removing the mods and everything from the mod just turned into update! or ate!upd blocks, but now in 0.15 it crashes. This seems unrelated though because I hav loaded other previously modded worlds and they load fine.
When loading most of my worlds, they load fine and I can play them, but when loading my superflat world, the game crashes when I try to move or look around. I have previously used mods in this world, but I had loaded it in 0.14 after removing the mods and everything from the mod just turned into update! or ate!upd blocks, but now in 0.15 it crashes. This seems unrelated though because I have loaded other previously modded worlds and they load fine.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
Luke W Your bug report was closed as Invalid as it appears to be caused by the use of third party mods or applications. If you can recreate the bug in a vanilla environment then please feel free to let us know and it will most likely be considered by the development team.
In the mean time:
Please make sure that comments are related to reported bug and written respectfully towards other players and development team. Offtopic, arguments and insults will be removed and author will be banned.
I launched the game again (no Optifine) and the bug is fixed, so I can't get the crash log.
Ah, I didn't realize. Sorry!
But I can't use Realms on 1.10...
The issue seems to be caused by looking at extending/retracting pistons from far away, in creative mode in my case (I was building a redstone printer with pistons).
Fine Mojang, don't fix the update! and ate!upd blocks and break modding permanently. And, in case I didn't make it clear, I've PREVIOUSLY modded the world and those update blocks aren't showing up. It really is a bug, you losers just want to make all of my issues invalid, even when they're not duplicates. I'll just stop reporting bugs for minecraft completely, if THIS is what you mods are going to do.
So basically, you're saying Realms is a 3rd party server software.
How is this intended? There's an obvious mismatch between the texturing of the normal blocks and upside-down stairs, and this is even more noticeable with sandstone since the side texture is also designed to match up with the top. Additionally this has already been fixed for slabs, which use a separate model when placed in the top half of a block. I know this is a 5-year-old issue and my comment will probably just be ignored, but it's something that's been bugging me for years and I don't know why Mojang decided that this should be an "intentional feature".
This would be a problem with OptiFine, and not the game itself. You'll want to go to the OptiFine GitHub to report bugs in the mod.
I don't think this issue is a duplicate, I think it's referring to the fact that the piston animation is basically 2 frames when it can and should be smooth.
Whoa, someone else actually noticed this. The effect originally didn't work in multiplayer, hence why it was broken in 1.3 (that version changed singleplayer to run an internal server). This is something I'd really like to see fixed, though I doubt it will happen (the code was supposedly removed entirely in 1.8, and it's such a small detail that most people probably won't notice or care).
Oh right, affects 20w19a.
Confirmed for 1.16.1. Ran into this while trying to make a disabled variant for hoppers. Using multipart did not fix the issue.
Still happens in 1.16.4. These blocks use special rendering, which is probably why they don't render in minecarts. (Heads and a few other blocks use entity models instead of normal block models. Liquids use special models generated in code.) I'm not sure if this will be fixed, we'd have to wait and see what someone from Mojang says.
Why is this Won't Fix? Can an explanation please be provided? This also affects custom textures that use transparency elsewhere, and has broken one of my resource packs.
This would be intentional I think. Most blocks that require support are now able to be placed this way, and pop off when the door is opened.
I figured out the reason this happens. The crackiness textures are correctly being switched between, rather than being overlaid on top of each other as this issue would imply. The problem is that the low/medium crackiness textures contain parts of the high crackiness texture hidden in the alpha channel. Their opacity is low enough for them to be nearly invisible in an image editor, but just high enough to appear at full opacity in-game, making the crackiness levels look identical. My fix for this was to just select all pixels outside of the intended visible cracks and set their alpha channel to 0. I attached a resource pack with this fix: IronGolemFix.zip
.
Fixing this also appears to fix
MC-173834.The texture is supposed to be additive, seems like that's not working correctly on fabulous graphics.
No longer happens for quartz stairs since they use the same top/bottom texture now
I seriously hope Mojang reconsiders this being "intended" for other GUIs. This is the cause for numerous softlocks and does nothing but facilitate griefing (as you can trap a player in a nether portal with no way to access most of their items, or even call for help in chat). Whatever duplication bug it was meant to solve likely no longer happens, and even if it does, a proper fix should just be implemented.
Bedrock Edition has these as 3D models, so if Mojang ever changes their mind and decides to fix this, that would probably be the easiest way to do it.
Just because the PersistenceRequired tag isn't being set doesn't mean it was intentionally made that way. They could have easily just forgotten to make it do that. This should be reopened until Mojang confirms whether it was actually intended or not.
The camera is supposed to only tilt to the sides when taking damage from non-directional sources, the bug here is actually that it gets stuck tilting in the last direction you got hit from. The original behavior (from before damage tilt broke in 1.3) was that non-directional damage sources would randomly tilt the screen either left or right, so I'd imagine that behavior should just be brought back. I recorded a couple videos of the current (bugged) behavior and the old behavior.