Manual fixes required for EU4 gamestate data before parsing

[nickbabcock]

Manual fixes required for EU4 gamestate data before parsing

[nickbabcock]

Thanks for the report. I don't know what would cause this issue offhand. The good news is that I'm working on an updated engine that handles your attached save flawlessly. In the meantime, if I or someone else comes across a bugfix for this, I'll create a new release.

[nickbabcock]

Please try installing the @next package.

npm i jomini@next

It contains the new engine. Below is some sample code to get you started:

const { readFileSync, writeFileSync } = require("fs");
const { Jomini } = require("jomini");
const args = process.argv.slice(2);
if (args.length !== 1) {
  console.info("expected one argument for the file path");
  process.exit(1);
}

console.time("read file");
const buffer = readFileSync(args[0]);
console.timeLog("read file");

(async function () {
  let start = process.hrtime();
  console.time("initialize jomini");
  const parser = await Jomini.Initialize();
  console.timeLog("initialize jomini");

  console.time("parse text");
  const data = parser.parseText(buffer);
  console.timeLog("parse text");

  console.time("stringify json");
  const json = JSON.stringify(data, null, 2);
  console.timeLog("stringify json")

  const outFile = `${args[0]}.json`
  writeFileSync(outFile, json);
  console.log(`json written to ${outFile}`)
})();

The new engine is 3x faster and uses a third of the memory. I've tested on your uploaded save and it works as far as I know. Let me know if this works for you.

[nickbabcock]

Fixed in latest release