Can confirm fixed in 26.3 Snapshot 2. Thanks!
Could you also upload a picture of a bottom screen corner with the FPS, TPS or network graph enabled? I’m curious how it looks.
You lead off with a vaguely worded report which in no way conformed to the Bug Tracker Guidelines and which falsely claimed that husks would spawn reinforcements in a situation where frostbites wouldn’t. You’ve demonstrated no understanding of my explanations of the game mechanics or Mojira best practices, and would rather tell me to give Mojang the original vaguely worded report with no context, seemingly in the hopes of getting your desired behavior in the game (for, in all likelihood, a short period of time, given the inconsistency it would create with husks) by any means necessary and without regard to Mojira staff, Mojang or the game itself. Please be advised that such behavior is unhelpful and disrespectful to all involved, and you may face consequences if this continues to be a problem.
I’ve granted myself ownership of this report since I’ve already rewritten the whole thing, even though, as previously stated, I believe the behavior in 26.4 Snapshot 5 and later to be intentional. I stand ready to narrow this report to focus on frostbites and make a separate report for husks, should Mojang request it.
The cartography table is a crafting station, and this is how crafting stations work. You can also fill a loom with many banners and dyes and the output will show a single banner, or put a stack of stone into a stonecutter and observe that the output reflects a single stonecut. All of these workstations work the same as regular crafting- you are shown the output of a single operation, and to perform multiple operations you can either left-click repeatedly (to perform the operation as many times as you’d like) or shift-left-click (to perform all possible operations with the given inputs).
That zip file doesn’t contain anything useful. Are you sure you aren’t running into MC-108, or something else which has been reported before? If you’re sure it’s a previously unreported bug then please upload a video recording of the issue with the debug overlay (F3) enabled and showing the game version and system specs. You can record your screen using:
On Windows, the built-in Snipping Tool app (shift+win+S)
On macOS, the the built-in Screenshot app (shift+cmd+5)
Third-party software such as OBS
It is recommended that you trim, convert and/or reduce the quality of your recording so that it is under 10MB, as this will make the upload much quicker.
This report will automatically reopen when you upload your recording or otherwise reply.
This issue is already being tracked in MC-313212, so I have resolved this report as a duplicate.
I’m resolving this into MC-271385. If you feel that this is incorrect, please provided detailed reproduction steps showing that this issue is distinct.
Also happens with opened shulker boxes.
Can confirm, also happens with shulkers (in this case I gave it NoAI after placing it so that it wouldn’t attack me).
Can confirm in 26.4 Snapshot 8. After looking at every mob in the debug world, baby sheep are the only ones to have this issue. Baby cats and ocelots have the red band partially above their collision box, but the midpoint of this band is still inside their hitbox (meaning they do not suffocate), and all other mobs have the band fully inside their hitbox.
I get similar artifacts on M3 Max, 26.4 Snapshot 8, Vulkan, OIT, 32 chunk render distance, albeit further away from the affected blocks than you are. Seems like the same issue, so I will mark this as Confirmed.
In that case the best “fix” would probably be to detect that the screen is shaped like this and round out the chat input field appropriately, possibly shifting the text to the right if it’s necessary to ensure it all remains inside the field. Whether that’s worth doing is another matter- it’ll probably depend on whether Apple keeps or scraps this change with future Macs.
The issue of the unmentioned change in behavior is still tracked in this report, I have simply broadened the report to include husks since I find it highly unlikely Mojang intends for these two mobs to work differently in this regard (although if they request me to create a separate report for husks then I will).
It is better to have reports read “This is the full scope of the issue, and this is the cause, which is due in part to an unmentioned behavioral change” than simply “the behavior changed”, since the latter wording makes it more likely that Mojang will defer triage indefinitely or attempt a limited fix. If they choose the latter, an inconsistency with similar behaviors is created, which is then itself reported, resulting in the targeted fix being reverted. Even in the absence of an inconsistency, it is possible that the other behaviors (in this case, husk reinforcements spawning only under the sky) would be reported because the initial report (i.e. this one) wasn’t found during a search, and this would needlessly clutter the bug tracker and still run the risk of inconsistent resolutions. The route I have taken here pre-empts both of these potential issues.
Does MC-98142 describe your issue? (Example: Attack a mob with a sword while it is flashing red from taking fire damage and observe that your punch deals no knockback.)
If it does not, please upload a video recording of the issue with the debug overlay (F3) enabled and showing the game version and system specs. You can record your screen using:
On Windows, the built-in Snipping Tool app (shift+win+S)
On macOS, the the built-in Screenshot app (shift+cmd+5)
Third-party software such as OBS
It is recommended that you trim, convert and/or reduce the quality of your recording so that it is under 10MB, as this will make the upload much quicker.
This report will automatically reopen when you reply.
Do other fullscreen games or apps with content in the bottom corners of the screen have this same issue? (One image from Apple’s website suggests that they do, but it would be good to get confirmation that this quirk happens in multiple apps.)
OpenGL performance seems no better in Snapshot 8 compared to before, and may even be worse.
Vulkan performance (no video this time) is better than ever this snapshot so great work on that.
Down to 30-35 calls in 26.4 Snapshot 8, and the framerate is noticeably improved compared to Snapshot 7. Glad to see that further work is being done on this!
This also happens when you summon multiple ender dragons and one of them leaves the fountain while others are waiting to perch there. One such dragon was teleported, essentially, to -761, 1527, -1143 – thousands of blocks away!
Alright, I’ve rewritten and reopened the issue, but I suspect Mojang will call this intended (and I would agree with such a resolution). If they do, it means the frostbite reinforcement behavior in 26.4 Snapshots 3 and 4 was unintended. It’s possible that Mojang will wish to disable frostbite reinforcements spawning under the sky in ice caves after reviewing this report, but most likely they will not consider this behavior an issue (I do not see it as one, and fear that any attempt to change this behavior would cause more problems than it solves).
Can confirm. The top video is from 1.8.9, and shows the dragon fly to a point level to the player and charge at them. This sort of charge only happens in modern versions after it ends its perch. (You’ll have to forgive the lack of debug overlay, I was not actually able to toggle it– F3 activated Mission Control and Fn+F3 and Fn+ctrl+F3 had no effect.)
This short clip is from 26.4 Snapshot 10, and shows about as similar of a behavior as the dragon now performs in normal flight: diving down and shooting a fireball (which is easy to dodge). Definitely not the same.