Raconteur

It does not affect most players, and even for the players that encounter it, it happen only one time.

It's a bug because the reloading of resources when you quit the resource pack screen should only happen when you added/removed a pack, or changed the order in the list. It's not a priority because occurences are rares, but this is one of these bugs that give a feeling of a non polished game, even more when you now that it needs only one line of code to fix it.

I've fixed it in a mixin if you want to check:

https://github.com/Brancieq-Paul/Pack-Stack-Memory/blob/main/src/main/java/fr/paulbrancieq/packlistfeatures/mixin/GameOptionsMixin.java

(the only relevant method for our case is the first Inject in the <init>)

Still happens in 1.19.2.

Can be problem if you need to place a map in an item frame. If it's in the "out of the map" zone, the cursor do not display at all.

I can confirm. I can reproduce it.

You fabric is installed on the server ?

Still not enough informations. You need to provide logs like it was asked to you in MCL-22371. You issue will be close again. Plus, it's the wrong project, it's about the Minecraft launcher.

Update: the only problem that I can find is that the trade is blocked after that. You may consider that as a bug... I don't know.

I tested and yes, in the left list of items on the left, it say you can trade air. But if you try to trade, you can see that it's not possible, there is nothing to pick up in the trade result and the emerald is not consumed.

I assume that "air" is the default display when, for some reason, the item to trade is unavailable or invalid. For example this reddit post, the guy enter a wrong command and the item traded by the villager is invalid, and replaced by "Air": https://www.reddit.com/r/Minecraft/comments/ehgy6l/help_with_custom_villager_keeps_trading_air/

So I think it work as intended. I personally consider it as a unwanted easter egg.

I think this comment sounds more like a feature request than a bug report. This is not the right place for that.

Can you explain how you determined this? Have you really tested it?

We need more to help you. Can you provide the game logs ?

You need to provide the crash log.

It's odd. Can you upload the logs ? We can't reproduce without more information.

You can upload the 100MB map on an other platform and send the link for download here.

Can you describe a detailed process to reproduce the bug ?

Describe the bug more please. Are you on multiplayer ? Upload a screen with your F3 displayed...

You can report paper issues here: https://github.com/PaperMC/Paper/issues

Upload the map somewhere and give us the link please.

It is the same bug that was described in this video ?
https://www.youtube.com/watch?v=rV1yJ5uM6ng 

Please be more specific, what are the steps to reproduce the bug? What were you hoping to do? And finally, I have the impression that your report is rather aggressive. The goal here is to help developers spot the many bugs that any game may have, not to spit on them.

@[[Mod] ampolive|https://bugs.mojang.com/secure/ViewProfile.jspa?name=ampolive] , I've seen this issue too and it's not a duplicate. MC-183103 refers to the portal mechanic introduced in 1.15. The range was too large because the search for the game was looking for the portal in the surrounding chunks, in a box of 17*17 chunks centered on the chunk containing the ideal block portal of arrival. It means that if your portal block was on the bordure of a chunk, the maximal teleportation distance was 8 * 16 + 15 = 143. You can see the diagram illustrating this below.

1.15 teleportation limit:

In 1.16.2, they implemented a filter which acts after the detection of portals and which is supposed to bring the limit back to 128.

I represent it as a circle:

1.16.2 teleportation limit:

And the issue I reported is about this filter. It should be 128 blocks like on the schema, but it's 135 instead. So I think these issues are not the same.