[Design Issue] Frustrating UX regarding conflicts between user settings and 'Hardcore Mode'
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Problem: It is frustrating to resolve a conflict between the user settings and the restrictions imposed by Hardcore mode.
When the user starts a game in hardcore mode, if one or more user settings is incompatible, it notifies the user that Hardcore Mode has been disabled due to X setting.
- The setting in question that is conflicting is not specified clearly. The notification's description of the setting is vague in that multiple different settings can be the one it refers to.
- In the notification, there are no menu navigation steps that specify the location of the setting. Due to the high number of categories and settings, clarification becomes less of a convenience and more of a necessity.
- The 'Reset to defaults' hotkey option is misleadingly worded, suggesting that pressing it will reset everything listed to the default value. This is mainly due to the pluralization of 'defaults'. This can lead users to clicking the option once and assuming that the other settings were already on their defaults.
Solution 1: When the user selects hardcore mode and there is a conflicting setting, the game notifies that the conflicting settings has been overidden for the play session. The game then runs in hardcore mode as expected.
- This is already the case with most features that conflict with hardcore mode, like save states.
Solution 2: When the user selects hardcore mode and there is a conflicting setting, the user may click a button on the notification window to 'fix' the conflicting setting(s), or to 'dismiss' the warning and proceed with hardcore mode disabled.
- The 'fix' option can potentially only apply to the current gameplay session.
Solution 3: When the user selects hardcore mode and there is a conflicting setting, it outlines an exact navigation path with the setting's name listed verbatim, and what value it needs to be changed to in order to resolve the conflict.
- This may become unworkable if multiple settings are conflicting.
Solution 4: When navigating the settings menu, options that conflict with hardcore mode are highlighted with an alert symbol. If a menu category contains a conflicting item, the menu category is similarly highlighted. The alert is removed if the setting is changed to a compatible value. This may be done with a button next to the item.
Solution 5: Change the hotkey hint's description from 'Reset to defaults' to 'Reset highlighted option to default' to reflect its actual functionality.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Hardcore Mode conflict notification, the settings menu handling, and the hotkey label for “Reset to defaults.” Compare the existing behavior with the five proposed solutions and determine which approach is accepted; done should make conflicting settings clear and make the reset label accurately describe its scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100