1.1.0: New Features and Performance Improvements!
Been a long time since the last release which I think is great! It means the project didn't have any noticeable bugs! Buut, it turns out there were a couple missing features which are coming to you right now!
New Features
It is now possible to require players to use the serverside resourcepack when joining the server. This is thanks to a gracious contribution from @fewwan! Using the new /pack required [true|false]
command you can set this configuration value or just running /pack required
will show you the current state. Naturally, there is also a new option required
in the config to accompany this feature. (#1)
You can also now set a short informational text that will be shown to players when prompted to install the resourcepack. This prompt can be set using /pack prompt [<prompt>]
or removed using /pack prompt clear
. /pack prompt
will also show you the current prompt text. (This was once again suggested by @fewwan)
Prompts can be any JSON text (same as /tellraw
) but does not support selectors, scores, or NBT. I recommend checking out the minecraft.tools generator to see what's possible.
The new /pack info
command allows you to see the current configuration of Better Server Packs at a glance! It shows you the pack URL, its hash, whether it's required and your custom prompt (if set). If you haven't set a resourcepack, the command will show you that as well.
Tweaks and Fixes
- All
/pack
commands now only require permission level 3 instead of 4. This should not affect most players but may be significant if you have a more complicated rank-system for your moderators and don't use mods like LuckPerms /pack set
(disabling BSP) now correctly saves to the config. Oops- Reloading pack hashes now runs in a seperate thread. This means that the server will no longer hang during
/pack reload
or/pack set
causing huuuge lag spikes with large resourcepacks or slow connections.
Full Changelog: https://github.com/Fisch37/better-server-packs-fabric/commits/v1.1.0
First release. See the README for more details