[Feature] Journalcrawler should track and update notsoldbiodata.json about artemisscannertracker HOT 4 CLOSED

Done for today. Will check this one again tomorrow

from artemisscannertracker.

Trying to think of any pitfalls that this can run into.

Technically thers now a third way to create discrepancies which could be averted if the SellOrganics event would state system and body of the exobiology sold in the journals:

That is get the journal crawler to read through journals that end up with any set of notsoldbiodata.json.
Skip over a journal that has a resurrect event then have a "SellOrganic" event later where the code identifies that the whole batch needs to be sold.
-> is not a problem if we get a full track record of things from any point in the past to the present.
-> For now I'll be deeming the keeping a complete track of journals that does not have random missing "holes" to be used with the journal crawler sufficient to not run into this.

Gotta add this one to #11 sometime

Fixable Pitfall:
Though there is the off chance where we have two sets of journals with some overlap where notsoldbiodata gets something added in the first run, that shouldn't be there after the second set of journals are crawled.
-> Analyse event happens in the first set of journals and corresponding sell event happens in the second set.
-> needs another check where prexisting elements in the notsoldbiodata have moved to the soldbiodata side of things. in the journal crawler.

from artemisscannertracker.

Looking back at this I forgot to add the tracking for the unsold value and it took two more incremental updates of just minor fixes for me to finally finish this one properly.

from artemisscannertracker.

Next time I could go and read it properly the first time round.

from artemisscannertracker.