Options file is not overwritten on first startup

[MrBacon1-1]

Minecraft Version

26.1 (LTS)

Mod Loader

Fabric

Describe the Issue

When I launch the modpack after freshly installing it from Modrinth on the Modrinth launcher I launch it and it says that the options file already exists even though I've checked after downloading before launch that the options file does not originally exist everything else works as I tried grabbing the file stored in the config folder and replace it manually which worked. Therefore I'm assuming the options file is somehow created before the mod is loaded and it may think it already existed therefore it does not overwrite.

Logs

2026-04-30-1.log

[BlayTheNinth]

This is because the Modrinth App creates options.txt itself before launching the pack. It can be disabled in the Modrinth App Settings.

It's impossible for Default Options to know whether the options.txt was put there with intent or not, putting me in a lose-lose situation. However, keybind defaults should still work correctly as long as Modrinth's options don't already include the keys in question.

[MrBacon1-1]

Would it maybe be possible to check the creation date of the file and lets say if it was created within the last minute its overwritten or some sort of flag system where in the config file there is a value where you can check if the options file has been overwritten before.

[MrBacon1-1]

I installed the modpack that didn't include the options file in the version. Modrinth seems to only create the options.txt file when the play button is pressed.

[BlayTheNinth]

Would it maybe be possible to check the creation date of the file

That would not account for the cases where users actually want Modrinth to manage their options.txt.

What options specifically are you wanting to provide defaults for?

[MrBacon1-1]

I was hoping to use Default Options to be able to ship default settings such as enabled by default resource packs and some video settings render distance etc.

[BlayTheNinth]

I can look into adding better support for default resource packs that can work regardless of existing options.txts.

I think for the case of video settings, it's better for Default Options to just stand down and trust the launcher to know better when it does prefill the options.txt, even if in the case of Modrinth it seems to unfortunately be doing it without previous user opt-in.

[MrBacon1-1]

Ok thank you for your time.

[BlayTheNinth]

Opened #101 as a follow-up.