Resource Pack Troubleshooting¶
Common issues when setting up the resource pack system.
Pack Not Downloading¶
Symptoms: Players don't receive the resource pack prompt on join.
Solutions:
-
Check if the server is running:
If the pack is not available, the HTTP server may have failed to start. -
Verify the port is open:
- Ensure the port in
config.ymlis not blocked by a firewall -
Test from outside:
curl http://your-ip:8080/pack.zip -
Check
host-ip: - Set it to your server's public IP, not
localhost(unless testing locally) -
The IP must be reachable by players
-
Port conflicts:
- Make sure no other service is using the same port
- Try a different port (e.g., 8081, 9090)
Textures Not Showing¶
Symptoms: Items show the base material texture instead of custom textures.
Solutions:
-
Rebuild the pack:
-
Re-download on client:
- Disconnect and reconnect to trigger a re-download
-
Or press F3+T to reload textures
-
Check namespace:
- Ensure model paths match between config and resource pack files
-
Item model:
curiospaper:ring_slot→assets/curiospaper/models/item/ring_slot.json -
Verify JSON syntax:
- Use a JSON validator to check model files
- Common issues: trailing commas, missing brackets
Namespace Conflicts¶
Symptoms: Warning messages about conflicts when the pack is built.
Solutions:
-
View conflicts:
-
Resolve conflicts:
- Rename conflicting files to use unique paths
-
Or enable
allow-namespace-conflicts: true(not recommended) -
Check registered plugins:
- Multiple plugins may register assets with the same namespace
Server Won't Start (Port in Use)¶
Symptoms: Error in console about port already in use.
Solutions:
-
Change the port in
config.yml: -
Find what's using the port:
Pack Too Large¶
Symptoms: Players experience long download times or timeouts.
Solutions:
- Optimize texture sizes (use 16×16 where possible)
- Use PNG compression tools (e.g.,
pngquant,optipng) - Remove unused textures from registered asset folders