In what I'll optimistically label enthusiasm to use the app, a lot of users end up with an initial profile that has a lot of problems, and don't realize them until it's too late to do a clean reset.
The basic idea would be a tab or control that is similar to the Profile (i.e. a grid), but instead of the mugshots and plugin areas, have extra columns to indicate the field being changed, old value and new value. If possible, group them together by NPC, e.g. so one "row" has two sub-"rows' for face plugin and face mod if both are being changed.
For problems that are automatically correctible at startup, such as re-homing invalid mod selections to whichever mod has the plugin, this would be shown with some messaging at the top, e.g. "problems were detected and automatically corrected, please review".
Batch operations could be done with a right-click context menu, or the style that is more typical on web UIs where selecting multiple records causes a button to show up with the batch actions. I prefer the latter for its discoverability. Maybe to improve discoverability of multi-select, there could also be a checkbox next to each NPC (but this may be difficult to implement with WPF).
The main use case is not manual, however, but dealing with problems such as a deleted plugin or mod, where it's really useful to show users what the app has done before they try to build again, as soon as they start the app, and give them the choice to either lock in those changes (plugin was removed on purpose) or back out (either continue normally, or fix and restart the app). This has been explicitly requested once or twice, but I think it is also a case of something that most users just "don't know they need it" but will realize it once it's there.
In what I'll optimistically label enthusiasm to use the app, a lot of users end up with an initial profile that has a lot of problems, and don't realize them until it's too late to do a clean reset.
The basic idea would be a tab or control that is similar to the Profile (i.e. a grid), but instead of the mugshots and plugin areas, have extra columns to indicate the field being changed, old value and new value. If possible, group them together by NPC, e.g. so one "row" has two sub-"rows' for face plugin and face mod if both are being changed.
For problems that are automatically correctible at startup, such as re-homing invalid mod selections to whichever mod has the plugin, this would be shown with some messaging at the top, e.g. "problems were detected and automatically corrected, please review".
Batch operations could be done with a right-click context menu, or the style that is more typical on web UIs where selecting multiple records causes a button to show up with the batch actions. I prefer the latter for its discoverability. Maybe to improve discoverability of multi-select, there could also be a checkbox next to each NPC (but this may be difficult to implement with WPF).
The main use case is not manual, however, but dealing with problems such as a deleted plugin or mod, where it's really useful to show users what the app has done before they try to build again, as soon as they start the app, and give them the choice to either lock in those changes (plugin was removed on purpose) or back out (either continue normally, or fix and restart the app). This has been explicitly requested once or twice, but I think it is also a case of something that most users just "don't know they need it" but will realize it once it's there.