A server resource pack lets you decide how the game looks and sounds for everyone who joins — custom textures, a themed UI, new sounds — without asking each player to install anything. Minecraft prompts them to accept it, downloads it, and applies it automatically. The one hard requirement is that the pack file lives at a public direct download URL; this guide covers both ways to get there, starting with the one where the panel does it for you.
| At a glance | |
|---|---|
| You need | A Minecraft Java server |
| Time | Ten minutes |
| Plan | Any |
The easy path: the Resource Packs page
Open the Resource Packs page from your server menu. It searches Modrinth and CurseForge (switch source in the dropdown), with filters for sort order, category (adventure, decoration, utility), game version, featured, and open-source only, in card or list view.
Find a pack and install it, and here's the part that saves you the whole hosting headache: the panel downloads the pack, uploads it to Falix's own CDN to give it a permanent public URL, and writes that URL and its SHA-1 into server.properties for you. You don't touch a single property. Restart, and every player who joins is prompted to accept it.
🎯 Good to know: This is why the Resource Packs page is the recommended route even if you just want a quick texture swap — it solves hosting, the URL, and the hash in one click. The manual method below is for a pack you made yourself.
What actually got set: the five properties
However you install a pack, it's driven by five server.properties keys — the same ones you can edit by hand on the Properties page. Knowing them is what lets you tune the experience:
| Property | What it does |
|---|---|
resource-pack |
The direct download URL of the pack .zip. This is the only required one. |
resource-pack-sha1 |
The pack's SHA-1 hash. Lets clients verify the download and cache it so they don't re-download every join. Strongly recommended. |
resource-pack-id |
A UUID identifying the pack. Modern clients use it to manage which pack is applied. |
resource-pack-prompt |
The message shown in the accept/decline dialog ("Join with our custom pack?"). |
require-resource-pack |
If true, players who decline are kicked — the pack is mandatory. If false, declining just means they play with default textures. |
Hosting your own pack
Made a pack yourself, or have one the catalog doesn't list? Minecraft needs a URL that points directly at the .zip — not a Dropbox/Drive "preview" page, not a download-button page. A link that opens the file's contents in a browser tab is wrong; a link that starts downloading the .zip is right. Your options:
- Let the panel host it. If your pack (or a close-enough one) is on Modrinth/CurseForge, install it from the Resource Packs page above and Falix hosts it. Simplest by far.
- Host it yourself on a static site. Put the
.zipon a static website — a Falix static site, or any host that serves files at a plain, direct URL — and use that URL. This is the standard way to serve a custom pack you built.
Then set it up:
- On the Properties page, paste your URL into
resource-pack. - Set
resource-pack-sha1to the pack's SHA-1 hash if you can compute it (many pack tools show it; it's optional but makes downloads verify and cache). Leave it blank rather than wrong — a mismatched hash makes clients reject the pack. - Optionally set
resource-pack-promptand decide onrequire-resource-pack. - Restart and test.
⚠️ Heads up: When you update a self-hosted pack, either change the URL or update the SHA-1 to match the new file. Clients cache by hash — reuse the same URL and old hash and players keep the stale pack.
Verify it works
Join the server. You should see the accept/decline prompt (with your custom text if you set it), and after a short download your textures change. If require-resource-pack is on, declining kicks you — proof it's enforced. The Console also logs pack send/apply activity per player.
Troubleshooting
- "Failed to download resource pack" on join — the URL isn't a direct link to the
.zip, the host isn't public, or the file moved. Paste the URL into a private browser window: it must immediately download the zip. Packs installed from the Resource Packs page avoid this entirely. - Prompt appears but the pack doesn't apply — usually a SHA-1 mismatch. Either set the correct hash or clear
resource-pack-sha1and try again. - Players see the old pack after you updated it — clients cached by hash. Change the URL or update the SHA-1 so they fetch the new file.
- Everyone's getting kicked —
require-resource-packistrueand the pack is failing to download. Fix the URL/hash first, or set it tofalsewhile you sort it out. - Download is painfully slow / times out — the file is too big. Keep packs lean; huge packs stall the join for players on slow connections and some clients cap the size.
Next steps
- Make your server yours — the full
server.propertiestour, including these keys - Datapacks — change gameplay the same "players install nothing" way
- Host a static site — a place to host a custom pack at a direct URL
- Building a pack from scratch (folder layout,
pack.mcmeta, texture paths) is standard Minecraft — the community reference at minecraft.wiki documents it in full.