Open UnknownSerhan opened 6 months ago
I can confirm this bug. It seems the multiblock has to re-form every time the server restarts, which can kill the ignition. With a high enough injection rate of deuterium and tritium, re-ignition happens automatically. With D-T fuel, re-ignition does not happen without inserting another hohlraum. Also, water cannot be inserted into the fusion reactor if only D-T fuel is used.
There is no workaround for the issues I have listed, as feeding deuterium and tritium vs D-T fuel are mutually exclusive upon (re)forming the multiblock and the water is removed. Same MC and Mek versions.
Same issue. Spent 3 days trying to get this to work and researching every reason why it wouldn't.
Doesn't matter if I send D-T fuel, Deuterium and Tritium, or all of the above.
My reactor would ignite, but would not consume ANY fuel.
With an ultimate gas tank on reactor port normally this creates a buffer which gives time for AE2 to initialize. Since then, I no longer have any problems during a server restart. But it is known that ATM 8, 9 also had this "bug"
Unfortunately the issue occurs even with a full ultimate chemical tank feeding fuel to the reactor in the same chunk. So yes it is still a valid bug. We will see if 1.21 will have it, it probably will.
Issue description
Duplicate of https://github.com/mekanism/Mekanism/issues/7587, but happening in 1.20.1. I am using D-T Fuel fusion reactor, used lasers to ignite it (last issue was more about "resistive heater ignited" fusion). Everything related to fusion is stored in a single chunk and all chunks are loaded by a dimensional stabilizer. Ran![2023-12-12_23 37 39](https://github.com/mekanism/Mekanism/assets/69000972/23b7acc4-5f55-416e-bfb5-35a06fcd9983)
save-all
command before stopping the server.When the ignition stops, all reactor data is still stored inside (plasma and case heat etc), meaning just the ignition stops.
Steps to reproduce
Minecraft version
1.20.1 (Latest)
(Neo)Forge version
Forge 47.2.14
Mekanism version
10.4.5 (Latest)
Other relevant versions
No response
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
No response