Works fine the next time around when the file is generated, though.

For a quick reproduction, just nuke the config directory, it doesn't matter if BLS' config is kept or not.

Just a triviality, since 99% of the time that file is already present, but caught me by surprise when gathering up a modpack, heh.

Sure, I'll add one in the evening.

(Also, isn't it possible to basically overwrite splash.properties with your own version, that specifies enabled=false?)

I'm not at my laptop for another few days, so can I have a crash report? Also I think this is caused by the way I disable forges splash screen at the moment: mess up forge's splash screen state so it crashes and disables itself next time (which isn't the best way of doing in things, but it kinda works) I am going to fix this soon though

It is possible, but I would rather not mess with config files... Even if it is forge's own files, it's not ideal when coding it to work properly would be better

Also I don't think I need a crash report anymore, I'm pretty sure I've already reproduced the issue before :)

The issue still present.