Skip to content
RuneFist Studios

Get the models to your players

Resource packs

RuneFist can host its own resources. Nexo and ItemsAdder are not needed to deliver RuneFist content.

English manual · September 2026 · Development preview

In game/rf → Resource Pack

Choose a delivery mode

RuneFist hosting (embedded)

The normal standalone mode. RuneFist serves its own committed resource pack and sends it alongside other plugins’ packs.

External hosting

You host the generated RuneFist ZIP at an HTTPS URL. The URL template tells the engine where to send players; it does not upload files for you.

Nexo managed (optional)

Deliberately hand RuneFist delivery to Nexo. Use this only if you want Nexo to build and deliver the combined pack.

Disabled

RuneFist does not deliver a resource pack. This is not a way to make the models work without client resources.

Set up standalone hosting

  1. 1

    Allocate a separate port

    Ask your server host for an available TCP port for pack downloads. It must be reachable from your players’ computers; the Minecraft game port is not automatically the resource-pack port.

  2. 2

    Set the host in game

    As an administrator, replace the example domain and port with your real address. 0.0.0.0 is a listening address, not the address players download from.

    /rf pack host 0.0.0.0 8181 http://play.example.com:8181
  3. 3

    Test from outside the server

    Use Current Client URL to check the actual download address. Test it from another computer or network. A localhost URL only works on the server computer.

  4. 4

    Send the pack

    Use Send to Me, accept the prompt, then check Client Results for a successful load.

    /rf pack send

HTTPS through a reverse proxy

If you already run a reverse proxy on the same machine, bind to loopback and set an HTTPS origin. Forward /packs/ to that local port. Configure the proxy and certificate separately.

  1. 1

    Example for an existing proxy

    Use your own pack domain, not this example.

    /rf pack host 127.0.0.1 8181 https://packs.example.com

Understand the delivery screen

Committed Publication

The current generated resource pack. A publication is not proof that a player downloaded it.

Send on Join

Send RuneFist resources automatically when players join.

Required Acceptance

Require players to accept the pack. When Nexo manages delivery, its own acceptance policy applies.

Client Results

Check actual load results, including failed or declined downloads.

Current Client URL

The download address offered to clients. Use it to identify local-only or unreachable hosting.

Send to Me

Retry delivery to your own client after correcting a problem.

Using RuneFist alongside other plugins