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
Currently, the General Controls for FTB Quests are fixed, and it would be nice if we could bind things to other keys if we wanted or needed to.
For example, and perhaps I'm in a minority of people, I always re-bind my Open/Close Inventory key to Tab. As such, closing the menu for things with it has become a habit. When I'm not paying attention and go to close my Quest menu I press Tab instead of the key for opening/closing FTB Quests. Complete user error, that's on me for not paying attention and hitting the wrong key, but in doing so I regularly and accidentally go to the next chapter.
So, in this case, having the option to remove the bind (or at least bind it to a new key) "Next Chapter" (or any of the other controls) would be nice.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered:
Mod
FTB Quests
Description
Currently, the General Controls for FTB Quests are fixed, and it would be nice if we could bind things to other keys if we wanted or needed to.
For example, and perhaps I'm in a minority of people, I always re-bind my Open/Close Inventory key to Tab. As such, closing the menu for things with it has become a habit. When I'm not paying attention and go to close my Quest menu I press Tab instead of the key for opening/closing FTB Quests. Complete user error, that's on me for not paying attention and hitting the wrong key, but in doing so I regularly and accidentally go to the next chapter.
So, in this case, having the option to remove the bind (or at least bind it to a new key) "Next Chapter" (or any of the other controls) would be nice.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: