zQuestRank | Quest-Based Ranks 1.3.4

👁 Open Any Rank's Quests

Clicking a rank you are not on used to do nothing useful. A locked rank told you to finish your current one first, and a rank you had passed told you it was done. Fine for players, awkward when you just want to check Rank 5's quests and icons came out right.

The new zquestrank.viewall permission opens every rank in the /rank menu, locked and finished alike. Operators have it by default, and you can hand it to your staff through your permission plugin.

Normal players see no change at all. Their menu behaves exactly as it did before.

🔍 What You See In Preview

• An extra line on every rank you are not on, telling you it can be opened for a look
• The full quest menu of that rank, with its icons, objectives, info item and claim button
• A note on the info item and the claim button making clear this is a look only, not your own progress
• Quests always show as fresh, on purpose. The progress saved against you belongs to the rank you are really on, so showing it under another rank would give you wrong numbers
• The requirement list is checked against you for real, which is the useful part. You can see straight away whether a money line, a playtime line or a placeholder line is written correctly, without setting yourself to that rank
• Nothing can be claimed or delivered from that view. Clicking the claim button or a delivery quest tells you it is a preview. Nothing leaves your inventory and no rank is given

💬 New Wording

Three new lines under rank in your language file, added automatically on this update with your own edits kept:

• click-preview the line in the rank menu
• preview-note the look-only line inside the quest menu
• preview-only the chat line when you click claim or a delivery there

📦 Install

Stop the server, replace the old jar in plugins/ with zQuestRank-1.3.4.jar, and start it again. New keys are added to your files automatically and your own edits are left alone.

🛡 Your Config Edits Are Safe

Updating the plugin used to cost you work. Keys you had added yourself were dropped, and keys you had written in a different shape to the defaults were replaced. Anyone using a per-page arrow map or a custom menu title had it reset on every update.

From this build the updater can only add. New keys from a newer version still land in your files with their comments, at the right place. Anything already in your file stays exactly as you wrote it, in whatever shape you wrote it, including your own extra keys and notes.

There is now a safety net as well. Whenever an update is about to change config.yml or a language file, the old file is copied to plugins/zQuestRank/backups/ first, named after the version it came from, such as config.yml.9.bak. Nothing is copied on a plain restart, only on a real update.

🖼 Decoration Items

You can now place any item you like in the /rank menu purely as decoration. Give it a name and as many lines of text as you want, and it just sits there. It opens nothing, says nothing, and clicking it does nothing at all. Use it for a title across the top, an explanation of how ranking up works, server information, or a row of glass to separate sections.

gui:
  decorations:
    - slots: [4]
      page: all
      icon: OAK_SIGN
      name: "&6&lServer Ranks"
      lore:
        - "&7Complete the quests of your"
        - "&7current rank to move up."
        - ""
        - "&eYou are &f%zquestrank_rank_name%"

• slots which slots it fills, counting from 0 at the top left, left to right. List several and the same item is drawn in each. A single slot: 4 works too
• page or pages which page it shows on. Use page: 2, pages: [1, 3], or page: all
• icon a plain material, a material with model data (OAK_SIGN:1234), or an ItemsAdder item
• name and lore with & and &#rrggbb colours, PlaceholderAPI placeholders, and ItemsAdder images. Leave the name out for a nameless filler

Write them as a list or as named blocks, whichever you find easier to keep tidy. On start the console prints how many decorations it loaded, and warns you if two sit on the same slot of the same page or if a slot falls outside the menu.

Two things to know. Decorations are drawn over the ranks, so in auto menu mode a decoration will cover whichever rank lands on that slot. Either place decorations after the last rank or switch to manual mode and leave gaps for them. The page arrows are always drawn last, so you can never hide them and get stuck on a page.

🆙 New Ranks Unlock By Themselves

A player who has claimed the last rank in ranks.yml sits at the top of the ladder with nothing left to do. The day you add another rank and reload, every one of those players picks it up on their own:

• The new rank's on-reach commands run for them, so their permission group follows
• They get a chat line telling them a new rank is out, configurable as rank.new-rank-available
• An open menu redraws on the spot

Online players get it within a few seconds of the reload, everyone else the next time they join. No manual command for anyone, however many players are waiting at the top.

Players are also no longer pulled backwards. The plugin now remembers which rank a player actually claimed, so still holding the permission group of a finished rank cannot drag them back onto it with their quests reset. Demoting someone on purpose still works exactly as before.

🎨 ItemsAdder Images Everywhere

An ItemsAdder image inside a rank name now renders as a picture in every place the plugin writes that name, chat included. The promotion message, the broadcast everyone sees, and the quest messages all show it properly, and the broadcast is sent to each player individually so it renders for all of them.

Both ways of writing an image work everywhere, in menus and in chat: %img_yourimage% through PlaceholderAPI, and ItemsAdder's own :yourimage:, which works even without PlaceholderAPI. Console lines stay as plain text.

✏️ Menu Text You Control

Page arrows can say something different on each page. menu.previous-page and menu.next-page stay the general text, and adding the page number targets one page. Arrows can carry lore lines now too, general or per page.

menu:
  next-page: "&eNext page"
  next-page-1: "&eOn to the high ranks"
  previous-page-2: "&eBack to the first ranks"
  next-page-lore-1:
    - "&7Ranks IV to VI"

The quest menu can have a title per rank. menu.quest-title stays the general one, and a rank can override it by position (quest-title-1) or by its key (quest-title-vip). If a rank has both, the one by name wins, and ranks you do not list keep the general title.

You can force a page count. The next-page arrow only appears while there is a page after the current one, so it hides on your last page. Set gui.rank-menu-pages to keep it working past the end, useful when the next batch of ranks is still being written. Leave it at 0 to count pages from ranks.yml as before. A decoration placed on a later page also counts as a page on its own.

📈 Metrics

zQuestRank now reports anonymous usage stats: server version, player count and plugin version, nothing about your players. It runs on a background thread and never touches the main one. To turn it off, set enabled: false in plugins/ArrowStats/config.yml.

🧪 Compatibility

Minecraft 1.18 and newer. Plain Spigot is fine, Paper is not required. Everything works on Spigot: menus, quests, requirements, rewards, Vault, PlaceholderAPI, ItemsAdder and permission commands. The one thing Paper adds is item and mob names following each player's own game language, so on Spigot those names show in English.

📝 Upgrade Notes

Stop the server, replace the old jar in plugins/ with zQuestRank-1.3.3.jar, and start it again. New keys are added to your files automatically and your own edits are left alone.

If an earlier update reset your settings, this is the build to set them up on for the last time. Put your decorations and per-page arrows back once here and they will ride through every future update. Keep a copy of your config and language files before you swap the jar, as you always should, and check plugins/zQuestRank/backups/ afterwards.

One config gotcha worth knowing: the default file ships with an empty decorations: [] in the example. If you add your own decorations above it and leave that line in, YAML sees the key twice and the empty one wins, so nothing shows. Delete decorations: [] when you start using decorations.

📋 Version Breakdown