Complete WorldState.Data models for the worldstate parser.

[Erlite]

All of these models are returned by the worldstate api at api.warframestat.us, so we'll need to make C# models for every item returned to be used when deserializing from the JSON results.

• News
• Events
• Alerts
• Sorties
• Syndicate Missions
• Fissures
• Global Upgrades
• Flash Sales
• Invasions
• Dark Sectors (don't think these are used anymore?)
• Void Trader
• Daily Deals
• Simaris
• Conclave Challenges
• Persistent Enemies
• ICycle interface for cycles like Earth, Cetus and Orb Vallis.
• Earth Cycle
• Cetus Cycle
• Orb Vallis Cycle. Doesn't look like it's in the docs, but iirc it's been added to the api.
• Construction Progress for Fomorians etc.

If I missed anything please let me know.

[Erlite]

Alerts should be done, created AlertMission and MissionReward. However it seems like the worldstate doesn't re-use models often between each route, only with a couple of exceptions, is there any reason for that? @TobiTenno

[TobiTenno]

Because the data is pretty different between each route

[Erlite]

Ah alright, well that's not too bad.

[TobiTenno]

I've been pulling as many common fields into the base object, but it's pretty varied. I need to go through and clean up some of the responses like for Twitter. At some point, I'd like to write it in bicubic routes similar to what Nexus stats uses for their API that makes their docs largely auto-generated.

[Erlite]

It's not a big problem, I'm just surprised DE didn't think about making their API cleaner in the first place.

[Erlite]

Unable to do events for now since the docs say array of object and the api returns an empty array.

[TobiTenno]

You can see the possible fields on the js repo in wfcd/warframe-worldstate-parser

[Erlite]

I'll also make an interface for cycles.

[Erlite]

Sorties are done.