Repository navigation
docs: explain how import obtains world data - #666
Merged
Merged
Conversation
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
1 participant
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.
The README says users supply both import inputs, which leaves readers looking for a way to provide a cMaNGOS SQL dump. Explain that users supply their client Data folder and the import command downloads the pinned dump after consent, verifies its checksum, and imports both sources. Link to the detailed import instructions.
Closes #658.
What you verified
pull-classic-db.sh.git diff --check origin/mainpassed. The branch is based on the latestorigin/main.What you did NOT verify
Did not run an import or the Rust tests. This change only updates documentation.
Model: gpt-6-astra. Harness: Codex in T3 Code.