Use RandomIndexDB for questlines & entries#130
Merged
Conversation
Rongmario
approved these changes
Oct 27, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uses the random index database added in #113 for questline entries (the quests as an entry in a questline) and questlines (the questlines themselves). I believe because quests were changed to use random IDs but the quest entries were not, the bitset
idMapinSimpleDatabasethatQuestLineextends ends up being sparsely populated and expands to very large sizes, causing excessive memory usage.Should be a better fix than #129 for specifically questlines, although that PR may still have use in other databases that use
SimpleDatabase.