Direct answer
The require-resource-pack setting asks compatible Java Edition clients to accept the configured server pack to join. Enabling it without a working pack URL can lock legitimate players out.
Recommended procedure
- Get resource-pack delivery working first with
resource-packand its matchingresource-pack-sha1. - Test the ZIP download on at least one clean client and verify its content.
- Set
require-resource-pack=truein server.properties only after successful testing. - Provide a clear resource pack prompt if the server version supports
resource-pack-prompt. - Restart and test both accepting and declining from a non-operator account.
Why this matters
The requirement is an admission rule for the client’s pack download response, not a guarantee that a player will never modify their local textures. If a proxy or plugin manages resource packs, avoid conflicting senders.
Practical example: Example: make the pack optional first and test from a clean client. If it downloads, turn on require-resource-pack and ask a test player to decline intentionally. If the client is disconnected before receiving the resource pack, investigate authentication/network instead. Do not use this setting as an account security measure.
How to verify the result
- Confirm accepting the pack completes login and its content loads.
- Verify declining causes the expected refusal message.
- If every user is rejected, temporarily revert
require-resource-packwhile diagnosing URL, SHA-1 or pack-format errors.
Version and compatibility notes
- Bedrock pack distribution and Geyser pack handling are separate workflows.
- Do not use a private LAN address for a publicly hosted pack.
Official references
These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.