imtbl

@Hangekisobu: I am well aware. But I am not a C++ programmer, hence why I didn't find it appropriate to post a C++ snippet. I also labeled my code as "pseudo-code" because that's what it is; it's not JavaScript either, I merely made up a syntax that's hopefully easy to understand. It should be trivial to apply this idea in C++ instead.

This still seems to happen in the latest version (1.20.51 as of writing this).

Even villagers at Master level can (seemlingly randomly) change to a different profession if a job site block for that profession is in the vicinity; I am not sure about the exact distance, but my current workaround is to space villagers I trade with 100 blocks away from any other job site block to prevent them from changing profession.

Considering this issue has existed for at least almost 3 years now: is this really that hard to figure out/fix? This basically prevents us from living together with villagers that we want to be able to properly trade with.

As a programmer myself, a quick workaround I can think of (even if the root cause of this is hard to determine) would be to add a conditional check inside whatever code block is responsible for changing villager profession that checks if the villager has been traded with (I assume the game keeps track of the number of trades with that villager or some other metric, like his experience, that we can use for this check) and, if yes, return at that point (and don't change his profession), since a villager who has been traded with should never change profession again.

Pseudo-code:

// If the villager has already been traded with, he should never change profession
if (villager->numberOfTrades() > 0) {
  return;
}

To follow up on my initial comment here from March 16th:

Sadly, the issue still persists in 1.19.71.

It seems like the freezes are shorter now in 1.19.71 compared to 1.19.70, at least from our experience (often just around 5 seconds, compared to the 30+ seconds I've observed in 1.19.70), but also occur more often, although we can't find a pattern as to what specific action causes them.

I've uploaded a video (switch_stutter_freezes_1_19_71.mp4) where you can clearly see the freezes/stutter when me and a friend are just walking through (previously already explored) parts of our world.

We've also tried creating a brand new world, but that doesn't make any difference. We've also tried all the other obvious troubleshooting steps, including turning down the graphics settings, logging out and back in again, clearing the cache (which only seems to affect the marketplace?) and even reinstalling the game completely.

Since this issue happens for both our Nintendo Switch consoles and has started appearing for both of us at the same time, immediately after the 1.19.70 update, I am pretty sure some change from that update is causing these severe performance issues on Nintendo Switch.

I can confirm this has been happening to me and my friend too since 1.19.70. If me or my friend play alone on our Realm, performance seems fine, but once the other person joins we get severe (30+ seconds) freezes as well as generally a lot of stutters.

If one person plays on Switch and one on PS5, the person on Switch gets the freezes and stutter and on PS5 the performance seems worse than before the update too (with frequent stutters), but it’s not as severe as on the Switch.