Minecraft Version

1.20.1

What happened?

Can't open the client, crashes when getting to main menu.
"Exception caught during firing event"

How do you trigger this bug?

1. Install mod
2. Start client-
3. Wait.
   4 Crash.
   .. Profit.

Loader

Forge

Loader Version

47.0.3

API Version

N/A

Mod Version

customfov-forge-6.2.0+1.20.1.jar

Relevant Log Outputs

https://gist.github.com/Gbergz/8e88142b2a75d634cd6a2accc3f7b183

That's odd, I can't reproduce this. Was this your first time starting the mod? Do you have a customfov.txt file in your instance's folder somewhere? If so, can you share its contents?

Edit: If there is no customfov.txt file, can you share your full log output from the crash?

customfov.txt

Here's the customfov.txt file

Edit: Gonna guess the issue is mod conflict, since I do have other mods present in my instance.

Here's full logs: https://gist.githubusercontent.com/Gbergz/75cb5debc5f599d78160b7501884d2fc/raw/638f5490d8d0c182ae0f46cc0e17a7dfcc1af702/gistfile1.txt
And crash-report: https://gist.githubusercontent.com/Gbergz/b43f2116725f69faf787316d6791dba0/raw/d31e552d01adf38ef00c969a4a94970b3980c315/gistfile1.txt

Very strange, I'm not sure how your customfov.txt file could've ended up like that. Okay, can you try two things for me:

1. Delete customfov.txt and then try booting it up again. Does it still crash? If it doesn't, boot it up a second time to confirm.
2. Start a new instance with just Custom FOV and see if it crashes.

1. Did that, nothing new, same crash. Logs etc.
   

2. This does work, no crashes. So as I put it earlier I think it's a mod conflict of some kind.

I have no idea what could be causing this. It seems like something is somehow either nullifying the vanilla options or delaying their load somehow.

I'll see if I can make a suitable workaround for this.

In the meantime, if you are able, it would be very helpful if you could isolate the mod causing this in order to solidify a long-term solution.

I will go through every mod till it boots.
I'll post an update when I am done.

You don't need to go through every mod one by one, you can trim the mod list by half and work your way down instead so that it takes less steps and you can isolate half of the mods each time.

Also, I should clarify, the issue is that the customfov.txt file got malformed somehow. It will always crash if the game is started with that file intact. To find the culprit, you would need to delete the file each time to make sure it tries to generate a new one.

Yep the first you wrote there is what I was planning. Kinda wrote it wrong.

And for the second part. Glad you reminded me.

Alright, thank you very much. I'm able to reproduce the crash on my end now and I'll begin working on a solution to make the two mods work together.

Alright, I've found the mod causing this specific issue and it's Default Options.

Removing the customfov.txt file then removing that mod, allows the game to boot.

This should be fixed now in the new version, but let me know if it persists.

All fixed! Thanks :)