Skip to content

options.txt #6363

@ADD3M

Description

@ADD3M

Please confirm the following.

What parts of Modrinth is your feature request related too?

Modrinth App

Is your suggested feature related to a problem? Please describe.

The current issue is that each new Modrinth instance starts with a completely fresh configuration, meaning users must manually redo their settings every time they create or install a new modpack. This includes keybinds, graphics settings, audio preferences, and other options stored in "options.txt". For users who frequently switch between multiple modpacks, this becomes repetitive and time-consuming, and increases the chance of inconsistent settings or mistakes. A shared or reusable "options.txt" system would remove this friction by allowing consistent default settings across instances.

Describe the solution you'd like

Add an option to upload the user's desired "options.txt" file to be used as the default configuration for newly created instances. This would allow users to automatically apply their preferred keybinds, video settings, sound settings, resource packs, and other configurable options across all modpacks without having to manually reconfigure them each time. Ideally, users could choose whether to use a shared "options.txt" for all new instances or override specific settings on a per-instance basis, providing both convenience and flexibility.

Describe alternatives you've considered

Alternatives that could be used instead include manually copying the "options.txt" file into each new instance after creation, or using a dedicated “template” instance that is duplicated whenever a new modpack is needed. Another option is relying on in-game mods that sync or save keybinds and settings across profiles, though this depends on mod support and is not always reliable across different modpacks or Minecraft versions. Some users may also simply reconfigure settings manually each time, but this is time-consuming and inefficient compared to having a built-in solution.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions