EN FR

CustomiZer — Resource Pack Hosting

Choose how players download your pack: CustomiZer's built-in web server, or LobFile's global CDN.

← Back to Docs
In one sentence: set resourcepack.hosting to self and give CustomiZer a spare port, or set it to lobfile and paste an API key — CustomiZer uploads the pack for you after every build.

Contents

How hosting works Option 1 — built-in web server Option 2 — LobFile CDN LobFile error messages When the pack does not load Advanced options

How hosting works

CustomiZer builds one resource pack and sends each player a link to it. It builds several variants (one per client shader dialect, plus Feather and Lunar variants), and every variant a player can be offered is hosted. Where players download from is a single setting:

resourcepack:
  hosting: self      # or: lobfile
ModeWhat happensBest for
selfCustomiZer runs a small web server on your machine and serves the pack from it.Servers with a spare port they can open.
lobfileCustomiZer uploads the pack to LobFile and sends players a CDN link.No spare port, limited bandwidth, or players far from your server.
The built-in web server keeps running in lobfile mode. If an upload fails, players are offered the local URL instead, so the pack still works.

Option 1 — built-in web server

CustomiZer needs its own TCP port, separate from the Minecraft port.

  1. 1Get a second port. On a panel host (Pterodactyl and similar) open Network and add an allocation, for example 203.0.113.10:19114. The Minecraft port stays primary.
  2. 2Put that address and port in plugins/CustomiZer/config.yml:
    resourcepack:
      hosting: self
      url: "http://203.0.113.10:19114"
      port: 19114
  3. 3Restart, or run /zpack zip.
Why url matters. With url empty, CustomiZer uses the address each player connected with. That works on simple hosts, but behind Docker or a panel the server's own IP is usually an internal address players cannot reach — CustomiZer never advertises a private, loopback or CGNAT address, and logs a warning instead. Setting url removes all doubt.

Option 2 — LobFile CDN

LobFile hosts the pack on a global CDN. No extra port, no bandwidth used by your server, and players download from a nearby edge.

  1. 1Create a LobFile account and activate it from the e-mail they send you.
  2. 2Copy your API key from the dashboard (Dashboard → Account Info).
  3. 3Turn on Continuous Uploading in Dashboard → Settings → General, so a full account never blocks a new upload.
    Continuous Uploading makes room by deleting the oldest files on the account that are not marked as favorites — including files CustomiZer never uploaded. Mark anything you want to keep as a favorite, or give CustomiZer an account of its own.
  4. 4Set the mode and key in plugins/CustomiZer/config.yml:
    resourcepack:
      hosting: lobfile
      lobfile:
        api-key: "YOUR_API_KEY"
  5. 5Restart, or run /zpack zip. The console shows LobFile: N/N pack variant(s) uploaded.
The key can also come from the CUSTOMIZER_LOBFILE_API_KEY environment variable, which keeps it out of config.yml. The environment variable wins when both are set. CustomiZer never writes the key to the log.

What CustomiZer does on each build

LobFile error messages

If an upload fails, CustomiZer writes LobFile's own message straight to the console, because the cause is usually something on the account that you can fix yourself:

[CustomiZer] [ResourcePack] LobFile upload failed: HTTP 412 Not enough
storage space on your account, upgrade your plan or delete some files.
(hash=...); those players get the built-in web server URL instead.

LobFile's messages say what to do — activate the account, fix the API key, free up storage or file slots, or move to a plan that fits the pack. Act on the message as printed; this page does not copy them, since LobFile may reword or add to them at any time.

Until an upload succeeds, players are offered the built-in web server URL. If url and port are not set, those players get no pack at all, so it is worth configuring both even in lobfile mode.

When the pack does not load

Set resourcepack.debug-status: true, rejoin, and read the [ResourcePack] lines:

LineMeaning
OFFER … url=…The pack was offered. Check the URL is the public address.
[ResourcePack HTTP] GET … status=200The player's client reached the web server.
CLIENT … SUCCESSFULLY_LOADEDThe pack is applied.

Advanced options

These live under resourcepack.advanced and are not in the default config. The defaults suit almost every server. Older configs that keep these keys directly under resourcepack: still work.

KeyDefaultUse
bind-address0.0.0.0Local interface the web server listens on.
server_threads4Web server threads (1–64).
public-hostemptyPublic host used when url is empty, instead of the join address.
public-port0Public port when it differs from port (NAT). 0 means the same.
public-protocolhttpUse https only behind a reverse proxy that terminates TLS.
download-retries1Re-offers after a failed download (0–3). Declines are never retried.
retry-delay-ticks100Delay before a retry.
auto-formattrueDetect the pack format from the server version.
format / format-minor46 / 0Used when the version is unknown or auto-format is off.
A reverse-proxy URL may include a path, for example url: "https://packs.example.com/customizer".