Long-lasting rift refreshes can fail, locking players out of the rift

[hRobert12]

Modpack

FTB OceanBlock 2

Modpack version

1.3.3

Launcher

Other...

Has the pack been modified

No

Log Files

debug.log

Describe the bug

As seen in the logs, it appears that when the rift refreshes for a team, if the refresh takes too long, it starts to spew out file related errors and the refresh fails. This ultimately causes the affected team to be unable to use the rift after exiting.

Steps to reproduce

1. Install the pack on a slow hard drive
2. Enter a world and enter the rift
3. Exit the rift
4. Notice that the hard drive is constantly clicking and the rift refreshes fail, causing the rift to be "unstable"

You can exaggerate the issue by running /tick sprint 1d after exiting the rift.

Expected behaviour

The refresh to work correctly and the rift to allow me to enter again

Screenshots

No response

Additional information

I installed the pack using the FTB app and imported it into MultiMC. I launched the pack using MultiMC.

I suspect this is caused by the rift helper mod not checking if a refresh is already happening before kicking another one off (since the refreshes start every minute according to the config).

Note that the failed refreshes can only be observed in the game's logs. In-game the player is only told that the rift is still "unstable."

[Gaz492]

Thanks for reporting this, our developer will have a look over the mod and see if they are able to reproduce.

On a side note, if your hard drive is clicking you may want to check the health (S.M.A.R.T) data for it as clicking can be a sign that your drive is starting to fail.