Red ''error'' chunks when opening the nether dimension in 1.18 worlds using MCA Selector 1.17.1

[Fauvic]

Describe the bug
The chunks in any Nether (DIM-1) 1.18 dimensions opened, either 1.17 converted worlds or newly created worlds, contain red ''error'' chunks.

To Reproduce
Steps to reproduce the behavior:

1. Create a world in 1.18
2. Enter a nether portal for 1st time
3. Exit world
4. Open the nether dimension in MCA Selector 1.17.1

Expected behavior
No red ''error'' chunks. I'm not sure if this is only on my end, if it's only a incompatibility issue with 1.18 worlds in MCA Selector, or if these chunks have an actual issue. Refer to below context regarding RAM usage.

Screenshots and other files

Screenshot:

World file:
New World Nether Test.zip

Debug:
debug.log

Environment (please complete the following information):

• OS: Windows 10
• Java version: 16.0.1
• Version of MCA Selector: 1.17.1

Additional context
Add any other context about the problem here, e.g.:

• I noticed that the server is using much more RAM than previously, even if no players are in there. When I delete the nether dimension from the save file and restart the server, the RAM usage normalises (until a new ''corrupted'' nether is loaded for 1st time).
• Minecraft version used to generate affected parts of your world:
• Mods used that change Minecraft save files or add blocks to the game: Tried on both modded fabric and vanilla

[Querz]

Fixed in release 1.17.2