Statuses

These are the pack statuses that you can react on with actions. The can be used both in the commands and the config and are also available in some of the placeholders for PlaceholderAPI.

The list is more or less in the order in which they occur when a pack gets send (some are alternatives of each other like accepted and declined) and some might not trigger once other status were called. (E.g. no_permission/wrong_version stops any later statuses or declined leads to loaded or failed not occuring)

No pack can be send to a player because all that would be available on that server are restricted and the player doesn't have the permissions he would need for that pack

No pack can be send because all packs that would be available on that server have a pack format that would be incompatible with the player's client version or the client has the wrong type (bedrock) and can't receive packs.

A request to download the server resource pack is send to the client. Run before anything shows up for the user.

The player chose “yes” on the download screen or has the server pack enabled for this server entry in his multiplayer list

The player chose “no” on the download screen or has the server pack disabled for this server entry in his multiplayer list

The player finished downloading the pack and the client applied it

The client failed to download the pack, e.g. when the pack url is wrong. Check the client's latest.log file for more details!

The client/player failed to react on the server resourcepack sent prompt in the amount of seconds set in the config at “prompttimeout” If no extra actions for TIMEOUT are set the DECLINED actions are used

For 1.20.3+ clients:

The player finished downloading the pack

The URL provided wasn't valid

The client failed to (re)load the applied pack

The client decided to not do anything with the pack (e.g. the same version was applied already)