-
Notifications
You must be signed in to change notification settings - Fork 412
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
Add Option to limit projected fits to offensive/assistive modules #691
Comments
Instead of a dropdown, I like the idea of implementing it in the state column, or a different column that is similar to state. Have an icon that represents friendly / offensive. Need to double check effects that have incorrect markings for isAssistive / isOffensive. |
Reusing the state column would be clever, but my concern is that it might not be very obvious for the average end user. You would also need a 4 way toggle, off, all, friendly, hostile. There are legitimate use cases for applying both friendly and hostile mods, and we'd want to support projecting modules that may not be correctly setup to be flagged as friendly. |
Somewhat easy. We already have that for the fitting window. Could just cycle. But I am not 100% behind that since it's kinda ugly, hence idea for a new column, which is much more straight-forward
Yep. We may even be able to override this somehow, either in the effect file or manually when we do the conversion to SQL (we do this to manually set published flags on a few items, this would be a last resort type of thing). |
If we split it out, we'll have 6 options. 2x3=6 But this is a good thing, in my mind. ☺
Can we expose this in the overrides window? |
Feature request.
Either a drop down or checkbox to allow you to apply:
The reason for this is primarily boosting moving to being a local effect rather than designated fleet boosts. When setting up complex fleet scenarios, it becomes extremely time consuming to be constantly flicking back and forth between fits to turn on/off modules (or accidentally leave modules on).
This would allow us to have an explicitly set flag to make managing boosts and friendlies easier in the projected tab, and more readily identifying what's friendly vs hostile.
The text was updated successfully, but these errors were encountered: