ArchThunder762

Can we downvote an issue?
Everything gets in boats. and Minecraft physics never makes sense. The size of the mob hasn't mattered before. There are a great many mobs that are too big for boats and some that make it near impossible for the player to get in the boat themselves afterwards. Why should the camel be any different?

Just adding another photo, used my phone to show that the cursor is off to the side but first inventory slot is selected, deselects once the mouse starts moving but sure is distracting.

This issue appears to be limited to situations where both the back and side of the comparator are connected to the same power source. It doesn't matter the orientation of the comparator. If the power source is the same for both sides it seems like the comparator only wants to push through the power that is connected from the north or south, ignoring completely the east/west sources. which means a signal strength of 2 from the side could completely cut off a signal strength of 15 from the back.

Here is a world I have prepared to do some comparison testing. I have tested this on all the devices I have available to me and had several other people also test. While I'm not an expert on computer hardware, it did seem in general that the better the GPU the worse the performance, with some other variance for the capability of the rest of the device. Test world has area's spaced out with 625 of each test item in it. the loose items test has droppers to fire items all at once should the last batch despawn, items are spaced out so that they don't combine and stay as 625 individual items

I did include some comparison tests. One for loose items on the ground and also for signs with lettering and glow ink (as a known issue comparison)

Most of the devices were restricted to 60fps.

In keeping with report formatting.
Steps:
1. load test world with Newer Ray tracing capable device. And also with another device with older gpu, or lower quality gpu
2. use a resource pack, or xbox game bar to view fps.
3. look only at 1 test location at a time and compare fps between two devices

Expected results.
the device with the better hardware will have better fps while looking at item frames with items in them, than the lower end hardware.

Actual results.
The device with the better hardware will have significantly worse fps while looking. or at least significantly worse fps drop. while looking at filled item frames than when comparing other test results.

I feel this issue is somehow effecting only certain devices or hardware specs.

I will make an example world to share soon, But for now I'll state my observations. On a server I play on, one persons storage room causes some players to drop to 30fps or lower. Their storage room has hundreds of item frames with items in them. She never used to have issues there herself (running on a GTX1650) . But she recently upgraded to a new computer and now has an RTX 3060 card. Now she also has noticeable fps issues. I also upgraded from an old laptop, to a new computer with an RTX 3050, and I now have fps issues where I didn't before. Similarly another server member with an RTX has the frame drops (waiting on exact specs). I have also sent someone with an RX570 there and he ran at his standard 60fps the whole time and no issues.

In a test world, I filled a 25x25 area with empty item frames. And didn't have any fps drop.
once items are placed in the item frames I would drop from 60fps to 35fps.
I also tested with the same area using signs with full text (just the letter a until it wouldn't fit). this area lowered my fps to 10
hitting those signs with glow ink would further drop fps to 4.

I'll run the tests again on a fresh flat world and compare what hardware devices I have access to and update again with the results as well as the world download. My initial suspicions are that something is causing incompatibility with ray tracing capable cards when it comes to item frames and signs.

These worlds are running 1.19.10 But I believe the issue is older than that, we're just noticing it because we're upgrading our computers.

youtube video showing screaming goat command

I am including the world where I was breeding goats. unfortunately I killed off the 681 goats that I bred. I had to do that in stages since they were getting out of hand.
i started with 2 regular goats and bred until they were unmanageable. I then used the tag command to get an accurant count of goats. tag @e [type=goat]
After waiting for all the goats to grow up I held wheat to keep them near and moved around waiting to hear a screaming goat. As an extra check I had a resource pack applied that altered the screaming goat horns. No screaming goats were noticed. Having verified no screaming goats present yet. I'd breed as many babies as I could then Kill all the tagged goats via command and start the breeding cycle over again.

Expected results would be to see some screaming goats within the first couple hundred goats.

Actual results was zero screaming goats.

Now see the video I've linked. I also tested the summon minecraft:born_screamer command. This was done one at a time and then on a repeating command block.

Expected results would be a screaming goat every time.
Actual results were very infrequent screaming goats. I was surprised that I did eventually get some screaming goats so it seems there is some random chance happening with a command that should have a 100% succsess rate.

I suspect these two things are related.

The command to "

/execute @e ~~~ event entity @e minecraft:born_screamer" Does work fine though.
Resource pack to help visually see a screaming goat is also included.

I have been testing this issue both in solo worlds. local servers. and multiplayer servers. I've uploaded a video showing hunger being lost while walking.
I was unable to reproduce this until I started adding behaviour packs to my worlds that modfied the player.json file.
Specificially I tested a solo world with a "One Player Sleep" behaviour pack. I knew the server I usually play on hasn't updated packs lately so I compared an older version of the pack to the most recent one provided by our pack maker. What I found was the issue only showed up with the old pack installed.
Looking at the player json files I was able to finde the code differences that would explain what we are seeing.
If you have hunger issues, make sure that you don't have any packs installed with an old player.json file.

Please confirm whether there is a nearby bed for the required village.

I discovered an issue with the pack I had previously used in testing. it was only allowing slime spawns in swamps. I've copied the spawn rules writen by goldenhelmet and tested in a few biomes at varying y lvls to make sure slimes still spawn properly.
Old pack removed and updated pack is uploaded.

I found similar results with rabbit spawns when I was testing with my own version of a restricting behaviour pack. I've added my own behaviour pack. It's slightly different in method, but functionally does the same as the one Syo Ronpo added. With the pack I got 10 Rabbit spawns for rabbits in a 7 minute period. without the pack I waited 15 minutes and only got 2 rabbit spawns and I got too impatient to see how long it would take to get up to a comparable 10 spawns. (when I say spawn I mean successful spawn attempts, not rabbits. I'm ignoring the additional rabbits in their pack spawns and only looking at the instances where the command block reported it had rabbits to kill. )
this was in a 9x9 area that I was watching at y150. In a frozen ocean biome with snow as my spawnable surface.
When I verified that swamp spawns still worked right with the pack. it did feel like I was getting faster hostile mob spawns at values higher than y70, but haven't done proper testing to confirm.

playing on a server using a windows 10 computer. found my chests that spanned a chunk border to be broken. opening chests crashed the server. We are running on the 1.16.201 hotfix that was said to have fixed this issue. 

Another player today had the same issue and crashed the server twice before realizing the cause.