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
EVE 21.06 added Pirate Insurgencies to existing Faction Warfare Space
Since this layers on top of existing Faction Warfare (the system may still be amarr or minmatarr for example) but may have a FOB and an insurgency in an area, it would be It would be quite clunky to add many more fields to the existing https://esi.evetech.net/ui/#/Faction%20Warfare/get_fw_systems
Use case
Players enrolling in the new Pirate faction warfare looking for information from the tools they already use
Corporations and Alliances getting involved and organizing themselves around this new content
Authentication
No changes required, this is simply to replicate features that were created on TQ to their assocated endpoints
Example return
Propose what an example return might look like. E.g.:
[
{
"solar_system_id": 30002082,
"insurgent_faction_id": 500011,
"type": "FOB"# do the other systems have a type ? or is it FOB and non-FOB"corruption_level": 5.0,
"suppression_level": 3.6,
},
...
]
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:
Feature Request
EVE 21.06 added Pirate Insurgencies to existing Faction Warfare Space
Since this layers on top of existing Faction Warfare (the system may still be amarr or minmatarr for example) but may have a FOB and an insurgency in an area, it would be It would be quite clunky to add many more fields to the existing https://esi.evetech.net/ui/#/Faction%20Warfare/get_fw_systems
Use case
Players enrolling in the new Pirate faction warfare looking for information from the tools they already use
Corporations and Alliances getting involved and organizing themselves around this new content
Authentication
No changes required, this is simply to replicate features that were created on TQ to their assocated endpoints
Example return
Propose what an example return might look like. E.g.:
Checklist
Check all boxes that apply to this issue:
The text was updated successfully, but these errors were encountered: