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
When quests are pinned to the HUD they appear without any indication as to what they are. I have seen this cause a lot of frustration for ATM9 players - we get at least one person every couple of weeks coming in on the subreddit asking how to get rid of an accidentally pinned quest because they don't know what it is and can't figure out how to undo it.
Describe the solution you'd like
When quests are pinned, they appear on the HUD underneath a header titled 'Pinned Quests', or Active Quests etc.
Describe alternatives you've considered
Not a modder, so I've mostly just been telling people about it who don't know what pinned quests are so they're able to then figure it out. I guess if you're a modpack maker you could include a tutorial as to how to use quest pinning, but then wouldn't every modpack have to do that individually?
Image of issue below. Note that there is very little to indicate it is a quest at all.
The text was updated successfully, but these errors were encountered:
Mod
FTB Quests
Description
When quests are pinned to the HUD they appear without any indication as to what they are. I have seen this cause a lot of frustration for ATM9 players - we get at least one person every couple of weeks coming in on the subreddit asking how to get rid of an accidentally pinned quest because they don't know what it is and can't figure out how to undo it.
Describe the solution you'd like
When quests are pinned, they appear on the HUD underneath a header titled 'Pinned Quests', or Active Quests etc.
Describe alternatives you've considered
Not a modder, so I've mostly just been telling people about it who don't know what pinned quests are so they're able to then figure it out. I guess if you're a modpack maker you could include a tutorial as to how to use quest pinning, but then wouldn't every modpack have to do that individually?
Image of issue below. Note that there is very little to indicate it is a quest at all.
The text was updated successfully, but these errors were encountered: