Resource packs and Bedrock

Every /erank apply builds a Java pack and a Bedrock pack. How they reach players depends on what your server already has.

Standalone (no pack plugin)

eRankGenerator hosts the Java pack for you: /erank apply uploads it and sends it to everyone online. Players who join later get it on join. It’s sent as an extra pack, so it never replaces a pack your server already sends.

• The prompt players see is resource-pack.prompt-message.
• kick-on-deny: true kicks players who decline it; kick-on-fail: true those whose download fails.
• /erank resend [player|all] sends it again.

To host the pack yourself, upload plugins/eRankGenerator/output/java.zip after each apply and put its address in resource-pack.url. To send nothing at all, set resource-pack.enabled: false.

With a pack plugin

eRankGenerator finds ItemsAdder, Nexo, Oraxen or CraftEngine on its own. On every apply it writes the ranks into that plugin’s folder and runs its reload command, so the badges go out in the plugin’s own pack:

Those files belong to eRankGenerator: they’re deleted and written again on every apply, so don’t edit them. Each rank is a glyph with the same fixed character, so the badge you copied from /erank list works there too.

To install by hand, set integrations.auto-install: false and copy plugins/eRankGenerator/output/<Plugin>/ into the plugin’s folder yourself. To skip one reload command, leave it empty in integrations.reload-commands.

Bedrock players

Bedrock players get their own pack, with a half-size copy of each badge (the editor’s Bedrock 1x view shows it). They never get the Java pack, and are never kicked over it. eRankGenerator knows them through Floodgate, or Geyser if there’s no Floodgate.

Geyser on the same server

Nothing to do. eRankGenerator hands the pack to Geyser, and Bedrock players get the new one when they reconnect; Geyser doesn’t need a restart. The console says Geyser found on startup.

Geyser on the proxy (Velocity, BungeeCord)

After each apply, copy plugins/eRankGenerator/output/bedrock.mcpack into the packs/ folder of Geyser on the proxy, and restart the proxy’s Geyser.

Not using Bedrock

Set bedrock.enabled: false: the Bedrock pack isn’t built or sent.

When a badge doesn’t show

• An empty box or a strange symbol: the player doesn’t have the pack. Ask them to accept it (Multiplayer → Edit → Server Resource Packs: Enabled), or /erank resend <player>.
• The old picture: with a pack plugin, check its reload ran (the apply message says so). Standalone, the player gets the new pack at once; if they declined it before, they must accept it.
• Bedrock still shows the old one: the player has to reconnect. With Geyser on a proxy, copy the new bedrock.mcpack and restart it.
• Two badges look the same, or another plugin’s icon shows: another pack uses the same characters. Tell support which plugin it is.