MangoTune profiles now behave as a library of real MangoHud .conf files stored under MangoTune's own profile directory and applied into the active config target.
Still unresolved:
whether MangoHud's own preset feature should be exposed directly in the UI
how to explain MangoHud launch-time config/profile precedence without confusing it with MangoTune profiles
Goal:
keep the UX clear and avoid overlapping profile/preset concepts unless there is a strong product reason to expose them
MangoTune profiles now behave as a library of real MangoHud `.conf` files stored under MangoTune's own profile directory and applied into the active config target.
Still unresolved:
- whether MangoHud's own `preset` feature should be exposed directly in the UI
- how to explain MangoHud launch-time config/profile precedence without confusing it with MangoTune profiles
Goal:
- keep the UX clear and avoid overlapping profile/preset concepts unless there is a strong product reason to expose them
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
MangoTune profiles now behave as a library of real MangoHud
.conffiles stored under MangoTune's own profile directory and applied into the active config target.Still unresolved:
presetfeature should be exposed directly in the UIGoal: