feat(ownership): Add database schema and config for waystone ownership#145
Merged
Conversation
AtriusX
force-pushed
the
feat/waystone-ownership-schema
branch
4 times, most recently
from
June 24, 2026 05:19
b2a755b to
0282ecb
Compare
This introduces the database schema and configuration for waystone ownership, enabling players to lock waystones and control who can create link keys. Schema changes: - Add waystone_uuid, primary_owner_uuid, and is_locked columns to waystone_info - Create waystone_authorized_users table for per-waystone authorization - Add unique index on waystone_uuid Application-side UUID generation and validation is handled via WaystoneInfo.fromLocation() and UUID.fromString() in repositories.
AtriusX
force-pushed
the
feat/waystone-ownership-schema
branch
from
June 24, 2026 05:22
0282ecb to
2f19233
Compare
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
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.
This introduces the database schema and configuration for waystone ownership,
enabling players to lock waystones and control who can create link keys.
Schema changes:
Application-side UUID generation and validation is handled via
WaystoneInfo.fromLocation() and UUID.fromString() in repositories.