[DiscordArchive] You would need to add every single archived updates hash to the DB, wouldn't you?
[DiscordArchive] You would need to add every single archived updates hash to the DB, wouldn't you?
Archived author: Kitzunu • Posted: 2022-11-20T22:18:23.379000+00:00
Original source
imo it should be fized before next squash
Archived author: Revision • Posted: 2022-11-20T22:19:01.791000+00:00
Original source
Does the updater currently find a file, compare it to the DB and import it if it isn't already listed in the DB?
Archived author: Kitzunu • Posted: 2022-11-20T22:20:57.366000+00:00
Original source
I believe so. Im not 100% sure how it works. But it hashes every file, thats why if you update an existing imported file, it will be reimported and rehashed
Archived author: Nyeriah • Posted: 2022-11-20T22:21:10.775000+00:00
Original source
last time I checked it is a dep that does that job, its not in the core
Archived author: Nyeriah • Posted: 2022-11-20T22:21:17.897000+00:00
Original source
we just tell it where to look
Archived author: Nyeriah • Posted: 2022-11-20T22:21:29.022000+00:00
Original source
the hash check and stuff isn't on our end
Archived author: Kitzunu • Posted: 2022-11-20T22:21:38.780000+00:00
Original source
C++ standard library iirc
Archived author: Revision • Posted: 2022-11-20T22:21:54.667000+00:00
Original source
I see. I can see how I/O would suffer from adding archived updates. I also don't see how you would do it otherwise.
Archived author: Kitzunu • Posted: 2022-11-20T22:25:54.362000+00:00
Original source
One way to do it is to add a file that drops all world tables, which forces all base files to be run.
But that will only fix the issue for world
Archived author: Kitzunu • Posted: 2022-11-20T22:26:05.179000+00:00
Original source
Cuz we cant go about dropping auth and char haha