-
Notifications
You must be signed in to change notification settings - Fork 36
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] Optional Mods column #24
Comments
This is not programmatically possible in the current state. But I could add a single copy key button per mod |
Ah okay, was a suggestion for the future. Was hoping it would be maybe easier to implement in the re-rewrite. |
i was about to post a feature request for this one as well, cant wait for kast then :D |
I might take a crack at a PR to implement this. Manually managing optional mod keys is probably the biggest pain-point for me when using FASTER. |
Is your feature request related to a problem? Please describe.
Currently I'm managing optional client side mods through the client column in the mods view. This clutters it up (and also causes the server to launch with JSRS enabled). I'd like to avoid that.
Describe the solution you'd like
Have a separate column labelled "Optionals" or something like that which doesn't do anything but copies the keys over into key folder. That combined with your lovely import preset functionality would make it super easy to manage a approved list of optional mods.
Describe alternatives you've considered
Running optional mods in the client column. Cluttering server launch and sometimes causing issues with the "Setup mods and join" functionality.
Additional context
FASTER is the best.
The text was updated successfully, but these errors were encountered: