You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding this as a placeholder feature for all the miscellaneous changes around predictive profile generation - avoiding patches, identifying overhauls, etc.
This is a long-running, possibly permanently-ongoing "feature".
The text was updated successfully, but these errors were encountered:
For most form lists, we do actually want a "set equals" (renamed to be consistent with that behavior). For packages, however, the order is important, and USSEP and probably other mods sometimes do nothing _but_ change the package order for a particular NPC. This is actually a change in behavior.
#85
This is the minimum required to display and interact with a profile based on the new analysis and mod repository code, not counting the XAML changes to the main Profile page. Most of the WPF components are just extracted from the original Profile page, but made standalone in order to provide better view/viewmodel encapsulation.
Not "fully" tested but all of the basic flows seem to work when integrated with the main app (TBD in a later commit).
#85#64#61#51#49#37#26#22 (doesn't complete any of these, but advances all of them)
Adding this as a placeholder feature for all the miscellaneous changes around predictive profile generation - avoiding patches, identifying overhauls, etc.
This is a long-running, possibly permanently-ongoing "feature".
The text was updated successfully, but these errors were encountered: