You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempting to register two different Fan Processing Types results in a crash occurring. The crash report/latest.log files show that the "FanProcessingTypeRegistry.insertSortedType" method is at fault for the issue, from the "FanProcessingTypeRegistry.register" method.
I asked about it in the discord, but nobody could figure out why exactly the issue was happening.
If any more information needs to be provided, I'll gladly provide it, just let me know!
Reproduction Steps
In a development environment, attempt to register 2 or more fan processing types utilizing the base create mod registration as a reference/basis.
Run the game
Expected Result
For the game to load properly with both fan processing types functioning properly.
I found the issue, didn't realize that the "getPriority" method needed to be unique. I couldn't find any documentation on creating a custom fan processing type, so this might be a good idea to include considering that not a single person had noticed this.
Describe the Bug
Attempting to register two different Fan Processing Types results in a crash occurring. The crash report/latest.log files show that the "FanProcessingTypeRegistry.insertSortedType" method is at fault for the issue, from the "FanProcessingTypeRegistry.register" method.
I asked about it in the discord, but nobody could figure out why exactly the issue was happening.
If any more information needs to be provided, I'll gladly provide it, just let me know!
Reproduction Steps
Expected Result
For the game to load properly with both fan processing types functioning properly.
Screenshots and Videos
No response
Crash Report or Log
https://pastebin.com/FLPJJfeF
Operating System
Windows 11
Mod Version
0.5.1e
Minecraft Version
1.20.1
Forge Version
47.1.46
Other Mods
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: