-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fusion reactor issue while playing on server #46
Comments
After that, we use an official forge server (version: 1403) to test that, and try to exclude the influence of using cauldron. When we are running the fusion reactor, the server will spam following message: But the reactor works perfectly. Then, I turned off the GT achievements system in the config file, and solved the spamming issue. But this time, the fusion reactor won't work perfectly as it before, and the status will be switching between "Working perfectly" and "Hit with Soft Hammer..... |
According to several comparative experiments, there might be a bug involving the fusion reactor and the new achievement system,no matter your are running a vanilla server or a cauldron server. |
Also I had the same problem in the SMP |
should be fixed in 5.08.20 Did not MP testing so far. |
…ores Debug/deepdark ores
Fusion reactor seems not working correctly in a SMP game.
In the single player game,it seems everything goes right.
However, when i did exactly the same design on a public server ,something weird happend.
The fusion had successfully started,but not working continuously.Its working status was switching fast between "Working perfectly" and "Hit with Soft Hammer..... " about 5 seconds a cycle, and the output was only 1/5 of the normal.
If you don`t turn it off or cutting down the power supply,the reactor will keeping on adsorbing energy from e-net.And as soon as the storage reaches another 40M EU threshold ,the reactor will try to start another new reaction automatically consuming all energy and then start to recharge.
Tested on gregtech 5.08.19, cauldron server
The text was updated successfully, but these errors were encountered: