Ender pearl loading/chunk loading bug

Describe the bug
A clear and concise description of what the bug is.
Not sure what causes this bug but when I use the design from this video https://www.youtube.com/watch?v=lde6ip1QfQw (just a remote control pearl stasis chamber) building the portal without the chunk loader part(you don't need it as of 1.21.3 and no this has nothing to do with the bug), it works fine in creative but in survival it tps me back as soon as I go to the nether, I looked through the config file but I'm stumped on what could be causing this. Obviously I tested without the mod and it constantly worked in survival.

To Reproduce
Steps to reproduce the behavior:

1. Make remote control stasis chamber(https://www.youtube.com/watch?v=lde6ip1QfQw)(you don't have to make chunk loader just a nether portal)
2. Going into the nether results in immediate teleportation

Expected behavior
You stay in the nether after entering the portal and the game doesn't check reeling the fishing rod until you try to use it again or relog.

Screenshots

Runtime info (please complete the following information):

• OS: windows 11 64-bit
• Minecraft version: 1.21.3(fabric)
• Mod version: 0.3.0 alpah 0.337+1.21.3
• Mod branch: (fill this if you are not using the default ver branches)

Crash reports / logs

Other mods

Sodium
fabric api
lithium
scalable lux
mod menu
reeses sodium options
sodium extra
Checklist

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

Additional context
<

[ishland]

Please fill the issue template.

Please fill the issue template.

Alright, I think I did it, if something is wrong with my description please let me know.

[ishland]

Works for me on a 1.21.3 fabric server with only c2me and fabric-api with both creative mode and survival mode.
I built it the same way as the video and tried the it several times. Everything works as expected.
I did build the chunk loader anyways.

Works for me on a 1.21.3 fabric server with only c2me and fabric-api with both creative mode and survival mode. I built it the same way as the video and tried the it several times. Everything works as expected. I did build the chunk loader anyways.

So for some reason c2me and scalable lux combined(maybe lithium too) decrease the consistancy for me by about a third to half, on client and on server, idk why it's happening, it's not that important but it bugs me for some reason. Using c2me without scalable lux or scalable lux without c2me results in the remote stasis setup working like 95% of the time.

[ishland]

It is only happening for the first few tries, but nearly impossible after that.
The root cause is that the chunk containing the fishing bobber is left Entity Ticking for a few game ticks. Ticking the fishing bobber entity makes it realize that the player is gone and despawn, triggering the ender pearl.
From investigating the vanilla player ticket code, the mechanism does not guarantee that the player tickets will be immediately removed after the player enters the nether portal, which can leave the chunk containing the fishing bobber to be Entity Ticking for a while. The behavior here is technically correct but probably not desirable.

a9a15f8 should help fixing these broken contraptions.

It is only happening for the first few tries, but nearly impossible after that.

The root cause is that the chunk containing the fishing bobber is left Entity Ticking for a few game ticks. Ticking the fishing bobber entity makes it realize that the player is gone and despawn, triggering the ender pearl.

From investigating the vanilla player ticket code, the mechanism does not guarantee that the player tickets will be immediately removed after the player enters the nether portal, which can leave the chunk containing the fishing bobber to be Entity Ticking for a while. The behavior here is technically correct but probably not desirable.

a9a15f8 should help fixing these broken contraptions.

Thank you I think that fixed it.