[UUID DB part 1] Load UUIDs for residents, towns & nations early #7945
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.
Description:
Part 1 of my attempt at the UUID db
This PR moves UUID loading to earlier in the load process, to during the initial list loading section. This allows us to safely reference resident UUIDs in other resident files, town UUIDs in other town files etc. and decouple more things from being name-based.
If a town or nation has no saved UUID, it will be assigned a new random uuid, this is in line with the saving logic where this also happens.
For the flatfile db, this does mean we have to read the same files twice during the loading process. I've moved up the
uuid=line in the saving process so that only the first line has to be read, to reduce the impact on loading time.By making this pull request, I represent that I have the right to waive copyright and related rights to my contribution, and agree that all copyright and related rights in my contributions are waived, and I acknowledge that the TownyAdvanced organization has the copyright to use and modify my contribution under the Towny License for perpetuity.