Conflict Management UI/UX design

[Al12rs]

Overview

Ticket for designing UI/UX for file conflict management feature.

Problem details

Independently of what game is managed, since the app puts files in a folder, if two different mods, or a mod and the gameFiles contain files with the same path but different contents, then the app needs a way to determine which file should end up being placed in the game folder during Apply.

These occurrences are commonly called file conflicts (even though this might not necessarily be the best user facing name for them, due to negative connotations of "conflict").

If there is a conflict, that doesn't actually mean there is anything wrong, there is just a choice to be made by the user.
It is important for the user to have this choice, as it can have impact on the game, either ecstatically (e.g. texture conflicts), or even to avoid bugs (black face bug, purple texture bug, etc, when not matching mesh model is used, or not matching NPC data is used).

While any game can have file conflicts (e.g. install the same mod twice), they can be more or less common depending on the modding methodology of the game.

If a game has mods be installed in separate folders (e.g. SDV, Bannerlord) or has most mods packaged into single archives (e.g. Cyberpunk .archives, BG3 .pak files), the likelihood of a file conflict is quite low.

If a game has mods be installed all in the same directory as loose files (e.g. bethesda games, BG3 Data mods), then the likelihood of conflicts becomes much higher.
In particular for bethesda games, the conflicts are very common, making this a very important feature to have for them.

Objective:

Give users an intuitive and powerful way to determine conflicts winners.