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 doesn't seem to be any way to project something onto a fit.
We need to be able to project entire fits. We may also want to project single modules. Pyfa does this currently, but it's often not particularly useful as it just uses base stats which are often far off from the actual stats (especially when bonused hulls are in play).
For modules (if we want to support them, which again I think is of limited use) we just need a state of:
Online
Offline
For fits we need four states:
Offline
All
Friendly
Hostile
The reason for the extra states is that it is currently painful to project fits when they have mixed modules in Pyfa. If my command ship alt has links and neuts, and I project it onto my Vengeance, then my Vengeance will show that I am getting neuted when that will never be the case.
This will become especially bad with the way that CCP is planning on command bursts, where you might have 10+ ships applying command bursts. By being able to sets a projecting ship to friendly, you only allow the beneficial modules to apply (bursts, logi, remote sebo, etc).
Conversely, if you set it to hostile, you can filter out any friendly modules.
Alternatively, we could separate out online/offline from friendly/hostile/all. In current Pyfa we already had the online/offline code, so @blitzmann and I had discussed simply adding a new column for friendly/hostile/all so we didn't have to touch online/offline.
Not sure which is easier in Eos, but either solution would work.
The text was updated successfully, but these errors were encountered:
Ebag333
added a commit
to Ebag333/eos
that referenced
this issue
Oct 24, 2016
Posted by @Ebag333
Currently doesn't seem to be any way to project something onto a fit.
We need to be able to project entire fits. We may also want to project single modules. Pyfa does this currently, but it's often not particularly useful as it just uses base stats which are often far off from the actual stats (especially when bonused hulls are in play).
We could do something like:
We need to support multiple states.
For modules (if we want to support them, which again I think is of limited use) we just need a state of:
For fits we need four states:
The reason for the extra states is that it is currently painful to project fits when they have mixed modules in Pyfa. If my command ship alt has links and neuts, and I project it onto my Vengeance, then my Vengeance will show that I am getting neuted when that will never be the case.
This will become especially bad with the way that CCP is planning on command bursts, where you might have 10+ ships applying command bursts. By being able to sets a projecting ship to friendly, you only allow the beneficial modules to apply (bursts, logi, remote sebo, etc).
Conversely, if you set it to hostile, you can filter out any friendly modules.
Alternatively, we could separate out online/offline from friendly/hostile/all. In current Pyfa we already had the online/offline code, so @blitzmann and I had discussed simply adding a new column for friendly/hostile/all so we didn't have to touch online/offline.
Not sure which is easier in Eos, but either solution would work.
The text was updated successfully, but these errors were encountered: