Brian Wilson

Finally got my hands on a Bounty event. Before patch 17 it was ```json { "timestamp":"2023-05-23T01:24:59Z", "event":"Bounty", "Rewards":[ { "Faction":"Federal Reclamation Co", "Reward":394907 } ], "Target":"krait_mkii", "Target_Localised":"Krait Mk II", "TotalReward":394907,...

All done.

Option A could be complicated to implement. We could take inspiration from https://github.com/EDDiscovery/BaseUtilities/tree/5125967c231f4d319e5bf7f28f97d662a15a4359/Audio (which takes a very different approach from EDDI but uses many of the same libraries). Option B...

Here's an English-translated version of the recognition loop: ``` {for body in SystemDetails(system.systemname).bodies: {body.shortname} {set bodies to bodies + 1} {if body.bodytype = "Moon" || body.bodytype = "Planet": {if body.alreadydiscovered:...

I'm not sure when or how it may have started but in short you seem to be having an issue with writing data to your SQLite database which is connected...

Yes, EDDI is designed to create EDDI.sqlite if if it does not currently exist. Do you know when the database errors started appearing in your logs?

I have no evidence for or against the repair script. All I know for certain is that the systemAddress is a unique contraint in the database and @nepomuk16321 's logs...

Thank you. Have you been able to confirm whether new the sqlite file has resolved the problem?

Thanks. :-) From that error message you might want to try disconnecting and reconnecting with the Frontier API.

I need the .log files from `%APPDATA%/EDDI` to see what may be causing EDDI to crash?