A small Geyser extension that allows defining the order of resource pack registration. PrioPacks does not add any resource packs by itself, but it can set the pack stack order for any resource packs added by Geyser's pack folder, other extensions, and so forth.
Download the PrioPacks.jar from the releases tab, and put it inside of Geyser's extensions folder. Then, restart Geyser, and you're done!
# PrioPacks Configuration
#
# Source: https://github.com/onebeastchris/PrioPacks/
# The below list represents the resource pack stack. Each entry is a uuid of a loaded resource pack.
# PrioPacks will then set priorities for each pack to ensure the order represented here!
# Resource Packs higher in the stack will be applied first on the Bedrock client (e.g. overriding a texture change).
# If this list contains uuids of resource packs that are not actually present, PrioPacks will gracefully skip over them.
pack-stack:
- e5f5c938-a701-11eb-b2a3-047d7bb283ba
- d9ee1211-b03e-43ec-b7f6-b7bcc7cf3fa4
# The highest priority that PrioPacks will assign to the top resource pack in the stack above.
highest-priority: 100
# The lowest priority that PrioPacks will assign to the bottom resource pack in the stack.
lowest-priority: -100
# The config version. DO NOT CHANGE!
version: 1After making the changes, you can apply these using /priopacks reload. To see all Bedrock resource packs that a Bedrock client got when connecting,
use /priopacks debug - this will print all resource packs of the first Bedrock client that joined after PrioPacks was started / reloaded.
There are two commands to make it easier to configure and use priopacks:
priopacks reload: reloads the configpriopacks debug: lists the resource pack manifests of the first Bedrock client that joined after priopacks was started or reloaded
The command permissions are priopacks.reload and priopacks.debug, respectively.