-
-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snooze quests #3952
Comments
note that you can restore quests in settings and reorder quests if you prefer different order (it fulfills some reasons for snoozing quests, but not all - is it enough for you use case? If not, what exactly you wanted to achieve?) See also #2562 |
Another workaround that I sometimes employ is:
That workflow preserves status of all other hidden quests. |
What quest would you want to snooze, and why? |
For example building quests. I (as well as SC default, as it should be) prioritize important information like Another time it might be the the road attributes of longer stretch of the road - I can see (for example) it is Or crossing quests (e.g. depending on time of the day/night and surrounding noise I might skip (Those are the few examples of different situations that come to mind; there are likely more but I'd have to pay attention and write them down) Note that it happens often enough to me that I've also developed quite a fondness of @Helium314 fork feature for |
This would be useful, but a good solution to #124 would be more useful for me. |
Hm well, I will not implement this the way it was suggested. That functionality would just open another bag of things that don't quite work for that use case: For example - how long will the quest be snoozed? Is it really possible to find any predefined time that would not feel unwanted in every case? I don't think so. #124 describes the root problem and that is that quests occlude one another, so that ticket is a better description would should be improved (if it was possible technically). |
For reference: Another idea from #4324: temporarily move one quest type to the end of the quest order. But it has the same problems as the ideas suggested in this issue. |
@FloEdelmann Thanks for your effort |
By the way: for me personally it would be enough if fading out of the task would be done for about 5 minutes |
Use case
When unable to solve a quest, the only option to see another one for the current node is to hide the quest completely or leave a note.
Proposed Solution
It would be nice to be able to snooze quests, so that they are not permanently hidden, but doesn't hinder one from resolving other quests for the same node.
The text was updated successfully, but these errors were encountered: