
Bug Report: ClassCastException when adding Fissible Fuel to Fusion Reactor
MidMeian opened this issue ยท 3 comments
Issue description
The game crashes with a ClassCastException when Fissible Fuel is sent to or present in a Fusion Reactor. The crash occurs in two scenarios:
Immediately when Fissible Fuel is added to the reactor or when accessing the reactor GUI while Fissible Fuel is present
Full Crash Report :
The game crashed: exception in server tick loop
Error: java.lang.ClassCastException: class mekanism.api.chemical.ChemicalStack cannot be cast to class mekanism.api.chemical.Chemical (mekanism.api.chemical.ChemicalStack and mekanism.api.chemical.Chemical are in module [email protected] of loader 'TRANSFORMER' @764db16c)
(full crash log : https://pastebin.com/wh1SDBG0 )
Environment Information :
Minecraft Version: 1.21.1
NeoForge Version: 21.1.192
Mekanism Version: 10.7.14.79 (Latest Alpha)
Mekanism Modules: All modules installed (Core, Generators, Tools, Additions)
Other Mods Tested With:
Applied Energistics 2
Various pipe/transport mods
Few other tech mods like oritech or industrial forgoing
Additional Context
This issue occurs consistently across different transport methods
The crash happens specifically with Fissible Fuel - other reactor fuels may not be affected
Issue persists even in minimal modpack setups
Server crashes immediately, making the world completlly inaccessible
Reproduction Rate
100% - This crash occurs every time the described steps are followed.
Steps to reproduce
Steps to Reproduce
Set up a Fusion Reactor multiblock structure
Attempt to send Fissible Fuel to the reactor using any of the following methods:
-Mekanism pipes/tubes (all tiers tested)
- Applied Energistics 2 (AE2) system
- Any other fluid/chemical transport method (pipz etc...)
OR Access the reactor GUI when Fissible Fuel is already present in the reactor (only able to reach this when using AE2)
Game crashes with ClassCastException: ChemicalStack cannot be cast to Chemical
Minecraft version
1.21.1 (Latest)
NeoForge version
21.1.192
Mekanism version
10.7.14 (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
I cannot reproduce this with only latest Mekanism installed on neoforge 21.1.192. I followed all the steps but no luck on reproduction. Which makes me think that there is another factor that might be causing this. I see some other mods in your crash report. Can you actually reproduce this issue while only latest Mekanism being installed on a fresh neoforge profile?