world refuses to load if c2me is present

[veccyboi]

Describe the bug
exactly what it says in the title. if I attempt to load into a world with C2ME in my modpack, my CPU usage shoots up to 100% (without it, it rarely goes much above 50%) and the world is stuck on the "joining world" screen

To Reproduce
Steps to reproduce the behavior:
install C2ME and all mods listed below

Expected behavior
the world would load normally

Screenshots

Runtime info (please complete the following information):

• OS: Windows 11
• Minecraft version: 1.20.1, forge 47.3.0
• Mod version: 0.2.0+alpha.1.1.15
• Mod branch: (fill this if you are not using the default ver branches)

Crash reports / logs
with C2ME: https://mclo.gs/v3BFwzK
without C2ME: https://mclo.gs/ggKDSad

Other mods
https://mclo.gs/Jy8Ukm7

Checklist

• [ x] I am using the official version of the mod.
• [ x] I tried the latest development version but the issue persists.
• [ x] I searched for similar open issues and could not find an existing bug report on this.

Additional context
sinytra connector was used. unfortunately, I do not have much time to do a thorough search of the minimal environment needed for this to happen, but i will see if i can get time to do so in the future

[ishland]

Log is truncated. Please use another paste site like https://paste.nolog.cz/ or https://paste.ee/

[veccyboi]

without C2ME: https://paste.nolog.cz/?ff0330ce22f77813#498MGGGp5e49QTM8HmhMivMQ7GuhdjKA1RfSV4qCkwWL
with C2ME: https://paste.nolog.cz/?ffb2d464e6dce089#GxWWVkCb4LPhrPQ652NFgENQErHYQs7qhFMqAqyeGyVt

[ishland]

Try disabling noTickViewDistance in the config file.

[veccyboi]

does this look correct?
[noTickViewDistance] # (Default: true) Whether to enable no-tick view distance enabled = false # (Default: 10) No-tick view distance max concurrent chunk loads # Lower this for a better latency and higher this for a faster loading maxConcurrentChunkLoads = "default" # (Default: true) Whether to use compatibility mode to send chunks # This may fix some mod compatibility issues compatibilityMode = "default" # (Default: false) Whether to ensure correct chunks within normal render distance # This will send chunks twice increasing network load ensureChunkCorrectness = "default"

because with these settings, the same thing still happens: the world is stuck on the loading screen and CPU usage shoots up to 80-90% (maybe something is stuck in a loop?)

log: https://paste.nolog.cz/?b93a134f7231c4bb#G4KFPvkmPBTScAJgq3ZaQYUfyafvyMUZyNnq4vD9Po7i

[ishland]

It's a mod compatibility issue or a sinytra connector issue at this point then. Try getting the minimum set of mods reproducible with binary search.