BellCubeDev / fomod-builder

A browser-based tool for building Fomod installers.

Fomod Builder

The Fomod Builder is a static Next.js project developed alongside the fomod library. It provides a simple and intuitive web interface for editing and building Fomod installers.

Browser Support

Supports all modern browsers. An Electron version may be down the road.

Important

Chromium-based browsers are recommended because they provide an API to access user-selected folders on the local file system with user consent.

Firefox supports most of the underlying API but, critically, does not support access to the local file system—rather, they limit it to virtualized file systems (which are, in every regard, useless to the Fomod Builder).

The Fomod Builder checks if it can use the API methods directly and will therefore automatically support Firefox and Safari if/when they choose to support the required API features.

Using

Warning

The Fomod Builder is still in early development. Some features may be broken or outright missing. You may not be able to complete a full Fomod installer. That said, if you encounter any issues, please report any issues you find!

Head over to fomod.bellcube.dev to use the builder! Have fun!

Local Copy

Open the project repository. Run:

npm i
npm run dev

FIXME

• Dynamic Length Inputs can stretch so far they push everything off of the screen

TODO

Needs Styling

• Option Editor

Roadmap

• Loader APIs
• Step/Group/Option Editing
• Install Editing
• Dependency Editing
  • Read ESP/L/M dependencies automatically
• TOOLTIPS FOR EVERYONE!!!
  Here's some tooltips we need:
  • Differences Between Mod Manager Implementations
    • SelectAtLeastOne Groups
    • (MO2) Name from Info.xml <Name> vs (Vortex) ModuleConfig.xml's <ModuleName>
    • MO2's CouldBeUsable extra space at start (needs further investigation)
  • Pseudo-Deprecated Features
    • CouldBeUsable Options
  • Problematic Features
    • NotUsable and Required Options
    • fommDependency
  • Intuition Breakers
    • First matching pattern determines Option behavior type

Potential Warnings

• Using an ESP module at all. ESM/L modules are preferred as they are handled more gracefully by the game engine.
• Importing more 3 or more files from a single folder in an option. Encourage using folders instead for maintainability.