When i click on a solid access port while the reactor dosen't have a control rod, its glitching out the interface, also the notic at the top dosen't disapear after a time

https://prnt.sc/10ving5

When i click on a solid access port while the reactor dosen't have a control rod, its glitching out the interface, also the notic at the top dosen't disapear after a time

https://prnt.sc/10ving5

Please define "glitching out the interface", thanks

It makes some interface stuff like health, food and armor bar looking really weird until you reconnect or break the block, see the link that i provided at the creation

I am running version 2.0.20 on 1.16.5 on a server using my modpack. Clicking the solid access port killed the server instantly with a stack overflow
[Crash log provided was wrong, continue thread]

I am running version 2.0.20 on 1.16.5 on a server using my modpack. Clicking the solid access port killed the server instantly with a stack overflow
crash-2021-03-13_14.43.09-server.txt

That's not what the crash report you linked is saying

When i click on a solid access port while the reactor dosen't have a control rod, its glitching out the interface, also the notic at the top dosen't disapear after a time

https://prnt.sc/10ving5

Please define "glitching out the interface", thanks

I am running version 2.0.20 on 1.16.5 on a server using my modpack. Clicking the solid access port killed the server instantly with a stack overflow
crash-2021-03-13_14.43.09-server.txt

That's not what the crash report you linked is saying

I am pretty bad at reading crash reports, however every time the block is clicked the server crashes, and single player too.
crash-2021-03-27_18.55.14-server.txt

I actually think I attached the wrong crash report above, first crash occurred today due to it, that was from 3/13, whoops

I am running version 2.0.20 on 1.16.5 on a server using my modpack. Clicking the solid access port killed the server instantly with a stack overflow
crash-2021-03-13_14.43.09-server.txt

That's not what the crash report you linked is saying

I am pretty bad at reading crash reports, however every time the block is clicked the server crashes, and single player too.
crash-2021-03-27_18.55.14-server.txt

I actually think I attached the wrong crash report above, first crash occurred today due to it, that was from 3/13, whoops

Your server is getting killed by minecraft own watchdog thread because something is causing a tick to take more than 60 seconds.

Please do the following:

1. remove performant and try again

2. enable the minecraft profiler (/debug start) to check what is taking that much time (a file will be generated in the debug directory in your server root when you stop the profiler with /debug stop)

thanks
Z

I am running version 2.0.20 on 1.16.5 on a server using my modpack. Clicking the solid access port killed the server instantly with a stack overflow
crash-2021-03-13_14.43.09-server.txt

That's not what the crash report you linked is saying

I am pretty bad at reading crash reports, however every time the block is clicked the server crashes, and single player too.
crash-2021-03-27_18.55.14-server.txt
I actually think I attached the wrong crash report above, first crash occurred today due to it, that was from 3/13, whoops

Your server is getting killed by minecraft own watchdog thread because something is causing a tick to take more than 60 seconds.

Please do the following:

1. remove performant and try again
2. enable the minecraft profiler (/debug start) to check what is taking that much time (a file will be generated in the debug directory in your server root when you stop the profiler with /debug stop)

thanks
Z

Alright, so I did what you said, I also figured out that every crash has been creating 2 crash reports.
The debug file is empty, like nothing on it.
Crash report 1 is time stamped 8:09PM:
crash-2021-03-27_20.09.09-server.txt
Crash Report 2 is time stamped 8:10PM:
crash-2021-03-27_20.10.10-server.txt

I believe the 2nd crash is due to the server's auto reboot failing (My host isn't amazing)

I am running version 2.0.20 on 1.16.5 on a server using my modpack. Clicking the solid access port killed the server instantly with a stack overflow
crash-2021-03-13_14.43.09-server.txt

That's not what the crash report you linked is saying

I am pretty bad at reading crash reports, however every time the block is clicked the server crashes, and single player too.
crash-2021-03-27_18.55.14-server.txt
I actually think I attached the wrong crash report above, first crash occurred today due to it, that was from 3/13, whoops

Your server is getting killed by minecraft own watchdog thread because something is causing a tick to take more than 60 seconds.

Please do the following:

1. remove performant and try again
2. enable the minecraft profiler (/debug start) to check what is taking that much time (a file will be generated in the debug directory in your server root when you stop the profiler with /debug stop)

thanks
Z

Updated my pack to contain the latest version, no more issues.