Exactly, this is the ONLY reason, to use this simple text file, which we (Navigraph) had created for many years to make our support more efficient. It´s nothing else as an information file which we provide.
But, and thats important - when it was our intention to use the file for parsing, we had used another format (like json, xml, csv, or any other structure format) to avoid EXACTLY such situations. All these 3rd party devs which uses this file has done this without asking if it´s ok, if the file is stable, will not be changed, removed … because in that moment, where I change anything in this file, we had the same situation. So for us, it´s a dead file which we can´t use.
This file goes back in FSX times, but in this time every add-on developer had designed his “own” cycle file which we supported. Started with LevelD, PMDG, ATR72, Fokker, … no one had used this file because it was clear for the “old” devs, that this file is just a info file (therefore the file name) in text format.
Cheyenne/Fokker, FS-Flightcontrol, … dataset:
PMDG, iFly, LevelD, AivlaSoftv1, … dataset:
FSC (FlightSimCommander) dataset:
SimToolKit, Pilot2ATC, … and so on, and so on … all these addons have used their own way. They have merged the cycle information which are necessary for their addon directly in their datasets.
Yes, I have reverted the code but the point here was, that I have also revert my whole workflow now with a lot of work on my backend systems, different tools and parsers. I have created over 100 file-formats in the last 20 years, not all are active but the testing-effort in the last days was enormous. As you possible know, we are also creating a new
cycle.json file for every add-on. This file is a structured file, which can easily read and where we can add tags/elements without loosing the other information. It´s a newer technology which we use now. But all these efforts are useless (at least for me) now because I must stay with this simple text file.
A personal note (I´m also only a human), I´m very disappointed about this discussion because my intention was to improve the service to bring it to a next level and not to remove something and to annoy someone.
I didn’t know that anyone was using this file to extract data, because if I had known, I would have announced it beforehand.
Revision 2 is out now and all datasets have now again included the
cycle_info.txt file. This file will not be removed or changed anymore.