Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
plugin:forceresourcepacks:faq [2024/03/23 09:49] – Add info about the download getting stuck phoenix616 | plugin:forceresourcepacks:faq [2024/10/30 09:26] (current) – change mcrp.host to mc-packs.net phoenix616 | ||
---|---|---|---|
Line 3: | Line 3: | ||
## Where can I host my resourcepacks? | ## Where can I host my resourcepacks? | ||
- | You can host your resourcepacks on any web server that supports HTTPS. If you don't have a web server you can use a service like [mcrp.host](https://mcrp.host) to host your resourcepacks. | + | You can host your resourcepacks on any web server that supports HTTPS. If you don't have a web server you can use a service like [mc-packs.net](https://mc-packs.net) to host your resourcepacks. |
## How do I set a resourcepack for a world? | ## How do I set a resourcepack for a world? | ||
Line 16: | Line 16: | ||
You can set a resourcepack for the whole network by using the `/frp globalassignment pack < | You can set a resourcepack for the whole network by using the `/frp globalassignment pack < | ||
- | |||
## How do I set a resourcepack for a specific version? | ## How do I set a resourcepack for a specific version? | ||
You can specify which version a pack is for by setting the `format` of the pack or the Minecraft `version` directly, either using the commands or the `packs` section in the config. | You can specify which version a pack is for by setting the `format` of the pack or the Minecraft `version` directly, either using the commands or the `packs` section in the config. | ||
- | In order to send different packs to different versions you need to use the `packs` section in the config file (right now there is no command for that, sorry) | + | In order to send different packs to different versions you need to use the `packs` section in the config file and add different packs to the [`variants` list](https:// |
## How do I disable kicking players for not having the resourcepack? | ## How do I disable kicking players for not having the resourcepack? | ||
Line 48: | Line 47: | ||
## Pack loading issues: | ## Pack loading issues: | ||
- | |||
### The download screen gets stuck at 100% | ### The download screen gets stuck at 100% | ||
Line 59: | Line 57: | ||
- Update to a client version that is at least 1.17 (as in that version Java was updated from 8 to 16) | - Update to a client version that is at least 1.17 (as in that version Java was updated from 8 to 16) | ||
- Install a modern Java version like 17 and manually specify it to be used in the launcher | - Install a modern Java version like 17 and manually specify it to be used in the launcher | ||
- | - Change the SSL certificate to one with a root certificate older than SUmmer | + | - Change the SSL certificate to one with a root certificate older than summer |
### The prompt closes immediately after it opens | ### The prompt closes immediately after it opens | ||
This is a bug in the Minecraft client that can occur when you teleport the player or force them to open an inventory after sending the resource pack. You can work around this by sending the pack with a delay or teleporting/ | This is a bug in the Minecraft client that can occur when you teleport the player or force them to open an inventory after sending the resource pack. You can work around this by sending the pack with a delay or teleporting/ | ||
- | + | ### The client | |
- | ### The client | + | |
When a server resource pack is send to a client it will shortly freeze after the download is complete. (Same as manually applying a local pack) This happens because the client has to reload all resources, check which resources overlap and do some other calculation and manipulation with them. (Like stitching all the textures together to a single image like they were in the first texture pack format) It's not a download issue as the client will locally cache the pack files and not re-download them if their hash didn't change. | When a server resource pack is send to a client it will shortly freeze after the download is complete. (Same as manually applying a local pack) This happens because the client has to reload all resources, check which resources overlap and do some other calculation and manipulation with them. (Like stitching all the textures together to a single image like they were in the first texture pack format) It's not a download issue as the client will locally cache the pack files and not re-download them if their hash didn't change. |