Powerplay Powerplay Data Links

I don't get it. Powerplay and BGS are all we have for an endgame. These are active communities that recruit and train players and give them something to do. Strategy, purpose, connection. But it takes data. The files we have weren't even that good, but now there are no files. Please give us data again so that we can grow the community.
 
Erroneous files

2016/08/11 - Star System Status http://hosting.zaonce.net/powerplay-data/2016-08-11/StarSystems11.08.2016.csv is the preparation list for the cycle

01/09/2016 - All files are incorrectly named. These are the correct names:
http://hosting.zaonce.net/powerplay-data/2016-09-01/Preparation1.09.2016.csv
http://hosting.zaonce.net/powerplay-data/2016-09-01/Prediction1.09.2016.csv
http://hosting.zaonce.net/powerplay-data/2016-09-01/StarSystems1.09.2016.csv

22/12/2016 - all files are missing. These are the correct names:
http://hosting.zaonce.net/powerplay-data/2016-12-22/Preparation22.12.16.csv
http://hosting.zaonce.net/powerplay-data/2016-12-22/Prediction22.12.16.csv
http://hosting.zaonce.net/powerplay-data/2016-12-22/StarSystems22.12.16.csv

Data missing for all cycles after 14 Sept 2017 (9 cycles so far).

Current Cycle files are stuck at cycle 119 (14 Sept 2017) and Previous Cycle files are stuck at cycle 118 (7 sept 2017)
 
Please give us some feedback on this. The files are really the only official way to get a proper view of the outcome of a cycle*, even though they're often gathered too early.

And while they aren't really being used for anything public these days, they are still very handy for the organizers to have, because they give us a bigger picture than we normally have.

* It is technically possible to figure everything out by comparing cycle upkeeps to default upkeeps, but only if no systems were lost, and even then it's a right pain to do manually as we're talking about 700+ systems with four values of interest for each.

To give you an idea of just how annoyingly slow this is to do, I grab screenshots from every single system listed in the PowerPlay menus (that's 717 control systems, 7 expansions and upwards of 99 preparations this cycle) and run that through OCR software. Gathering the screenshots takes ~15 minutes (1 second per screenshot plus moving between preparation/turmoil, expansion, control systems and each power), and the OCR bit takes about 1 second per system (so just shy of 15 minutes total), and since it's OCR I then have to manually verify that the names and numbers make sense (quite often my OCR software only grabs two digits for triggers for example), and before you know it it's taken an hour to get the raw information into a useful format, and I seriously doubt I'm the only one wasting my time doing this multiple times a week, every single week!

This is a computer game. All the information is ALREADY computerized and PUBLIC in the game. Why do we have to jump through these ridiculously stupid hoops just to be able to properly strategize one of the only parts of the game that requires preplanned strategies and cooperation between large numbers of people?!?

I realize that I'm beating a dead horse here, but for the love of Jameson throw us PowerPlayers a bone here. Move the PowerPlay data properly into the journals in one way or another (and before you ask the stuff that's currently in the journal is useless for organizing a power). Either kill off PowerPlay or give it the proper support it needs - it's currently stuck in a stupid vegetative stake, and it feels like FDev is looking at a document called "Do Not Resuscitate" and don't have the backbone and common decency to pull the plug!
 
Is there any chance of getting an explanation on how it works and what the problem is?

I've always wondered why the data came about an hour before tick and didn't provide the actual tick information.
 
How were these reports created? Is there some way to extract the information from logs, or was it all hand-entered?

They were machine generated at around 05:00 UTC every Thursday. Sadly it seems this was never properly automated, which is why there are cycles missing, and then out of the blue, after cycle 119, it just stopped.

There is currently no way to extract the information from client logs (not unless you want to very likely break the terms of service and do memory scraping or similar). The PowerPlay entries in the journal are useless for organizing a power, and is barely enough to figure out what it is an individual commander has done. There are no trigger information in the journal, there are no totals. If you have inbound merit transport of any kind, you need to work your way backwards through the journal to figure out where the merits were collected, and if you're carrying merits for multiple systems (something that often happens with inbound fortification), and you drop some, there's no indication whatsoever which merits were dropped.

There are a multitude of ways the journal data could be updated to make it a useful tool for PowerPlay, but so far those suggestions have been ignored.
 
Back
Top Bottom