[Crash] Fabric-1.20.1-21.0.2
Phoupraw opened this issue · 8 comments
First run: latest.log
Second and third run: latest.log
There is no crash report.
@Phoupraw Can you upload the attributefix.json config file? The error is from reading whatever is in the file. It's either incorrect or generating incorrectly.
@Phoupraw Can you upload the attributefix.json config file? The error is from reading whatever is in the file. It's either incorrect or generating incorrectly.
The attribute, "trifle:flying_duration", is from my mod. Its max value is infinity.
Oh okay, that would explain the issue. Java's BigDecimal doesn't support infinity and NaN values. I've pushed through an update that should be compatible with your mod. Delete the config file again and let me know how it goes. https://www.curseforge.com/minecraft/mc-mods/attributefix/files/4844657
Oh okay, that would explain the issue. Java's BigDecimal doesn't support infinity and NaN values. I've pushed through an update that should be compatible with your mod. Delete the config file again and let me know how it goes. https://www.curseforge.com/minecraft/mc-mods/attributefix/files/4844657
By the way, could you please make it not to directly crash but log it (maybe error or fatal) and regenerate it, when meeting broken config file? That would make issue tracking easier.
Based on the first log your config file for this mod is invalid. Please delete and regenerate the config and try again.
Based on the first log your config file for this mod is invalid. Please delete and regenerate the config and try again.
The first run log is already a log after I deleted the config and relaunched the game.
@Phoupraw Did the new release fix the crash you were having? There is already some protections to regenerate the config file however this issue was a different case as it couldn't generate the initial config to write so the loading could not proceed.
@Phoupraw Did the new release fix the crash you were having? There is already some protections to regenerate the config file however this issue was a different case as it couldn't generate the initial config to write so the loading could not proceed.
Yes, the new release fixed the crash.