Skip to main content
Resource Pack Assistant background
First-party pluginPublic plugins
Resource Pack Assistant icon

Resource Pack Assistant

The Resource Pack Assistant download page with the current package, overview, version history, and docs.

Treat resource-pack delivery as a managed workflow instead of hoping players click through it correctly.
Support both plugin-config and server.properties sourcing, including a hot-update-friendly panel workflow.
Keep player self-service commands and admin controls close to the same pack pipeline.

Runtime

Spigot 1.15.2 / Java 8

Admin tools

/rpa, /textures, config.yml, server.properties mode

Primary systems

Join-send, status tracking, fallback send, enforcement, auto-reload

Stage

Live release

Latest release

Resource Pack Assistant

The Resource Pack Assistant download page with the current package, overview, version history, and docs.

  • Treat resource-pack delivery as a managed workflow instead of hoping players click through it correctly.
  • Support both plugin-config and server.properties sourcing, including a hot-update-friendly panel workflow.
  • Keep player self-service commands and admin controls close to the same pack pipeline.
Browse plugin directory

Overview

Resource Pack Assistant handles the human side of pack delivery: asking for the pack, tracking whether the client accepted it, retrying or enforcing where appropriate, and giving players or admins commands to recover from a bad state.

The server.properties mode makes the plugin especially practical for hosted servers where one panel-driven file is easier to update than a scattered plugin config workflow.

At a glance

  • Treat resource-pack delivery as a managed workflow instead of hoping players click through it correctly.
  • Support both plugin-config and server.properties sourcing, including a hot-update-friendly panel workflow.
  • Keep player self-service commands and admin controls close to the same pack pipeline.

Compatibility and setup

Runtime

Spigot 1.15.2 / Java 8

Admin tools

/rpa, /textures, config.yml, server.properties mode

Primary systems

Join-send, status tracking, fallback send, enforcement, auto-reload

Stage

Live release

Guide

Resource Pack Assistant purpose banner

Purpose

Make resource-pack delivery deliberate instead of fragile

This plugin exists so your server can treat the resource pack as part of the onboarding flow, not a hope-and-pray prompt.

RPA tracks accepted, declined, failed-download, and loaded states, then gives you clear options for resend, fallback, or enforcement.

That matters because the pack is often part of the server identity. If the delivery flow is messy, the first impression is messy too.

Overview

  • Join-send behavior and tracked client pack states.
  • Optional resend or kick-after-time enforcement.
  • player-side helper commands and admin resend controls.
Resource Pack Assistant quickstart banner

First Boot

Choose where the pack URL lives before you tune the reminders

The first real decision is whether pack data should stay in the plugin config or move into server.properties.

RPA supports the legacy plugin-config path and the more convenient server.properties path. For many servers, the second option is better because it keeps the pack URL and SHA1 in the same place the panel team already knows.

YAML
pack:
  source: SERVER_PROPERTIES
  send-on-join: true
  server-properties:
    url-key: "rpa-resource-pack"
    sha1-key: "rpa-resource-pack-sha1"
    auto-reload: true

That one choice has a big effect on how easy the pack pipeline is to operate later on.

First boot

  • The plugin is reading the pack source you actually want to maintain.
  • Join-send and fallback behavior make sense for your player flow.
  • Players and admins both have a clear way to recover from a failed pack load.
Resource Pack Assistant features banner

Standout Features

The server.properties mode is what makes this plugin especially practical

RPA is strong because it respects the way real hosted servers are often managed.

The plugin can read standard or custom keys from server.properties, auto-reload those values, and still preserve a vanilla-first or plugin-fallback pack flow when that makes sense.

That is a very practical design for teams that already update pack URLs through a panel and do not want the pack pipeline split across several different admin habits.

Why the workflow is better than a basic pack prompt

  • Pack source can live where the hosting team already works.
  • Fallback logic keeps the flow resilient instead of brittle.
  • Self-service player commands reduce needless support tickets.
Resource Pack Assistant showcase banner

Showcase

Show the onboarding prompt, the admin status view, and the recovered player flow

Resource Pack Assistant is easiest to trust when the page proves the workflow around the pack, not only the config file.

A strong gallery should show one player-side prompt, one admin status or resend surface, and one clean success state where the server looks right after the pack loads.

That demonstrates both the technical and user-facing value of the plugin.

Gallery

  • The pack request feels readable to players.
  • Admins can inspect and recover bad states quickly.
  • The final loaded state is worth protecting.

Gallery

Preview slot

Resource Pack Assistant in a live server scene

A real in-world shot that shows Resource Pack Assistant doing its job instead of hiding behind a menu.

Preview slot

Resource Pack Assistant admin tools

A clean admin, editor, or config view that proves the plugin is practical to run.

Preview slot

Resource Pack Assistant final payoff

A polished result that shows why the plugin belongs in a production server stack.