Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] Option to rescan game Journals #2548

Open
Darkcyde13 opened this issue Jun 10, 2023 · 1 comment
Open

[Request] Option to rescan game Journals #2548

Darkcyde13 opened this issue Jun 10, 2023 · 1 comment
Labels
9. enhancement The behaviour is as specified, but we would like to modify or extend the spec. significant work Just sayin'

Comments

@Darkcyde13
Copy link

What happens now

If corruption happens in the EDDI database (ie. loss of scanned and mapped timestamps like in 4.0.3-b1), there is no way to correct this.

What I'd like to happen

EDDI to have the ability to repopulate corrupted entries in the database.

How it can happen

I posted on the EDSM GitHub page as suggested by T'kael on the forums, and received a reply (I assume from a user, not the dev) who suggested requesting a feature for EDDI to rescan all game Journals to repopulate any corrupted data.

I guess this would be much like an EDSM 'obtain logs', but be faster as the data is all local. Of course, if the game logs are missing, this would be ineffective. Looking at my own game logs, they only go back to December '22, so this wouldn't help with anything before that time, but would be valuable for anything I do have a log for.

EDDI Version

v4.0.3.-b2

@Tkael
Copy link
Member

Tkael commented Jun 10, 2023

This could be possible but EDDI would need search through every journal entry rather than using summary data provided by EDSM and EDDI would be to support every version of the journal that has been released rather than just current entries (which until now it has not been built to do and which might make this a more difficult request to implement).

@Tkael Tkael added 9. enhancement The behaviour is as specified, but we would like to modify or extend the spec. significant work Just sayin' labels Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
9. enhancement The behaviour is as specified, but we would like to modify or extend the spec. significant work Just sayin'
Projects
None yet
Development

No branches or pull requests

2 participants