-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature Request: Key binding #13
Comments
Hi, I'll try implementing this, it might take a while |
Here you go |
Thank you so much, Timmeey86 for taking a look into it. It works nicely so that you can assign individual keys to the function. Great! It's just a question. This is you mod of course. I can live with it so I have to learn to be careful when having less than 100 % in the baler. :D But thanks anyway!! |
I think the default binding just uses "Tool Function 4". I don't think it's a good idea for a mod to change the binding for Tool Function 4 since there are also other things bound to that by the base game |
Hi Timmeey86! Thank you for the mod that early in FS25 history!
Apparently the key binding for unloading unfinished bales is hard coded, am I right?
I'm playing FS25 primarily with a XBox controller atm and have two key bindings in the F1 menue for "Unload unfinished bale early". One is the standard key binding for unloading (finished) bale (RB + Y) and additionally there is LS + DPdown. As I accidentally unloaded unfinished bales by mistake I wanted to reset the default RB + Y to not take effect for the mod but only for the ingame standard (unloading finished bales) and only use the second LS + DPdown I figured there is no key binding option for this mod in the key binding screen but think that would be great (in my case especially for avoiding unloading unfinished bales by mistake via the standard key binding RB + Y).
Long story short: As long this isn't a bug on my side I would like to suggest to implement the possibilty to set the key bindings – if you like and if it's possible.
Thanks for reading!
The text was updated successfully, but these errors were encountered: