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
I'm not sure if it'd be better to just expose the fuel bay contents directly, or do something fancier like this. Either would work and would be very handy.
I specifically ask for fuel contents as a raw number because, for example, the cyno jammer structure is frequently going to sit offline with no consumption but it would need fuel inside it for when it is needed.
Checklist
Check all boxes that apply to this issue:
Feature request description is provided
Use case exists
Feature requires a new route
Feature adds data to existing route
Feature requires new auth scope
Feature can reuse existing scope
Feature does not require auth
Meta feature, applies to all routes
The text was updated successfully, but these errors were encountered:
Why stop at fuel block and liquid ozone count? The endpoint should expose all structure specific "hangars" and their items. The ability to enumerate what ammunitions are present, their counts and even what fighters are loaded in the tubes would remove a lot of the guesswork that goes into managing a citadel.
Please note that this information is already available through the corporation assets endpoint.
Since structures are corporation assets, they will show up in the corporation assets endpoint, along with all their corporation-owned contents, which includes the exact contents of their fuel bay.
This feature request is only about making this fairly important bit of info available in a more direct manner.
GIB FEATURE
The new jump gate flex structure is going to use liquid ozone as an irregular consumable. It would be great if we could track it.
Currently the /corporations/{corporation_id}/structures/ endpoint exposes "fuel_expires" which is a direct function of consumption.
I want to add something similar.
Add a new structure to that with the same permissions but work like this:
(Don't take out "fuel_expires", that's nice)
I'm not sure if it'd be better to just expose the fuel bay contents directly, or do something fancier like this. Either would work and would be very handy.
I specifically ask for fuel contents as a raw number because, for example, the cyno jammer structure is frequently going to sit offline with no consumption but it would need fuel inside it for when it is needed.
Checklist
Check all boxes that apply to this issue:
The text was updated successfully, but these errors were encountered: