zCustomGear - Armor Sets & Talismans 2.8.1

📊 Naming Both Sources

If you put %corejobs_external_xp_source% on a scoreboard, it names zCustomGear while a set is worn, then reads as no source once the set comes off, even with a CoreJobs boost still running.

That is correct behaviour. The external placeholders are about other plugins only, and a boost the player bought inside CoreJobs is not another plugin. The payout was always right either way.

CoreJobs 1.5.0 adds the line that names both:

Swap xp for money or farmpoints. Use total for a general "your bonuses" line, and keep external for one that is specifically about outside plugins.

How CoreJobs names itself in that list is yours to set, in its own language file:

placeholder:
  self-source: "&bCoreJobs"

Change it to whatever your players call it in the shop. Set it to Server Boost and the line reads Server Boost, zCustomGear.

📦 Install

Stop the server, replace the old jar in plugins/ with zCustomGear-2.8.1.jar, and start it again. No config changes, nothing to reset.

Update CoreJobs to 1.5.0 if you want the new line. 1.4.0 still works exactly as before, you simply do not get total_..._source. On 1.4.0 you can put two lines side by side instead: %corejobs_total_xp_amount% for the real total, and %corejobs_boost_xp_multiplier% for the CoreJobs part.

📦 Crates

You can now make crates. A crate is an item a player right-clicks to open. Opening it uses one from the stack and gives rewards, which can be an item, one set piece, a full set, a talisman, a talisman bag, or a console command.

Each crate is one .yml file in the new crates/ folder, exactly like sets and talismans. A starter.yml is created for you on first start, so you have a working example to copy.

Two ways to pick rewards, set with roll-mode:

• weight (the default) always gives the number of rewards you set in rolls, and each reward's chance decides how likely it is against the others. Give them all the same number and they are equally likely
• chance rolls every reward on its own percent, so chance: 25 means 25 percent. One open can give several rewards, or none at all

A reward with guaranteed: true is always given, in either mode.

The odds are worked out for you. Turn on show-rewards-in-lore and the crate item lists its rewards with the percentages filled in, using %reward% and %chance% in your own line format. You never type a percentage by hand, so the lore can never drift from what the crate actually does.

Other keys worth knowing: rolls, unique-rolls, require-empty-slot, keep-on-death, and sound. Set require-permission: true to lock a crate behind zcustomgear.crate.<id>, otherwise anyone can open it.

/zcg crate list
/zcg crate info <id>
/zcg crate give <player> <id> <amount>

With require-empty-slot: true, opening with a full inventory is refused and the player keeps the crate, so nothing is lost.

⛏️ CoreJobs Bonuses

A worn set or an active talisman can now boost CoreJobs payouts, the same way it already could with EcoJobs. Three payouts, each with its own key:

bonuses:
  integrations:
    corejobs-xp-multiplier: 1.25          # +25% job XP
    corejobs-money-multiplier: 1.10       # +10% job money
    corejobs-farmpoints-multiplier: 1.50  # +50% farmpoints

Leave a key out and that payout is untouched, so you can give more xp without giving more money. A set and a talisman that both boost xp multiply together: a 1.5 set with a 1.2 talisman gives 1.8. A boost the player already bought keeps working, and the gear stacks on top of it rather than replacing it.

Turn the whole thing on or off with integrations.corejobs in config.yml.

This needs CoreJobs 1.4.0 or newer. On an older build the bonus stays off and the console tells you to update.

📊 The Bonus Is Visible Now

The gear bonus used to be invisible. A player with a 2x set got double xp, but %corejobs_boost_xp_multiplier% still read 1, because that placeholder means the boost the player bought. Players read that as the gear being broken.

zCustomGear now reports what it is giving, so these include the gear:

Swap xp for money or farmpoints. There is nothing to switch on, it works as soon as both plugins are running, and your existing scoreboard lines keep working because %corejobs_boost_xp_multiplier% still means what it always did.

✨ Glow Keeps the Rank Prefix

A glowing armour set used to strip a player's rank prefix and name colour, whether that came from TAB, LuckPerms or Nametagedit. Now the glow applies and the rank display stays exactly as it was, and the original name colour comes back when the armour comes off.

The glow also returns on its own after a relogin or a respawn, instead of needing the armour taken off and put back on.

Keep PacketEvents installed for this. Without it the plugin still runs, but the rank prefix can disappear while glowing again. The console prints one line if it is missing.

🎨 Glow Colour or Name Colour

Minecraft uses one colour for both the glow outline and the name above the head. They are the same setting, so a coloured glow always colours the name too. That is a Minecraft limit rather than something a plugin can work around.

You can now choose which one wins:

glow:
  recolor-nametag: true

• true (the default, and how it behaved before) the glow shows the set colour and the name matches it
• false no team colours are touched, so the name keeps its rank colour and the glow shows in the rank colour instead, or white for a player with no rank

Reload with /zcg reload after editing. Nothing changes for you unless you change this option.

Want a gold glow and a red name at once? That needs a name tag plugin that draws names with display entities, such as UnlimitedNameTags or DisplayNameTags. The name is then drawn separately and is not tied to the glow colour.

📋 Version Breakdown

📦 Install

Stop the server, replace the old jar in plugins/ with zCustomGear-2.8.0.jar, and start it again. Your sets, talismans and bags all keep working, and the new keys are added to your config.yml automatically.

Two things to have in place: PacketEvents for the glow, and CoreJobs 1.4.0 or newer if you want the job bonuses.

The example set file now ships with a CoreJobs xp multiplier in it. That only affects a fresh install using the example as it comes. Your own set files are never edited, so nothing changes on a live server until you add the keys yourself.

🔧 What Changed

Talismans are now one per slot and never join into a stack.

Before, the same talisman could pile into a stack, which tripped up the talisman bag: a full stack of four went in at once, but if you split it and tried to add just two, the bag wouldn't take them. The bag checks one talisman at a time, and a stack hides items behind a single slot. Now every talisman is its own single item, so the bag takes them one by one, every time, no matter how you move them. Timer talismans already worked this way, and normal talismans now match.

📌 Note on Older Talismans

Talismans you handed out before this update may still stack with each other. To make them single items, give them again with /zcg talisman give. New talismans are always single from now on.

📦 Install

Stop the server, replace the old jar with zCustomGear-2.5.1.jar, and start back up. Your config, sets, talismans, and player data stay the same.

🎒 Talisman Bag Fixes

• No more eaten items: because the default bag is a bundle, items could slip inside it when dragged or clicked onto it with your inventory open, and both of those paths (dropping an item on the bag, and picking the bag up to click it onto an item) are now blocked. To store talismans, right-click the bag to open its screen and place them there.
• Live contents list: the talisman list on the bag now updates on its own while the bag is open, no need to close and reopen.
• Instant effect changes: pull a talisman out of an open bag and its bonus stops the moment it leaves, even with the screen still open.
• No duplicate talismans: a bag won't take a talisman it already holds. On by default, and you can allow copies in the config.
• Cleaner blocked-item feedback: when an item is rejected, the plugin refreshes your inventory so the client drops the leftover sound. (Bundle items still make Minecraft's own small bundle sound, switch the bag to a non-bundle material to remove it entirely.)

🔖 Cleaner Talismans

• No weapon stats: talismans that use a sword or tool as their item no longer show attack damage, attack speed, or the "Minecraft" line. Talismans are passive, so those numbers are hidden now.
• Text updates on reload: change a talisman's name or text and run /zcg reload, and items players already hold update on their own, no need to re-give them. Timer talismans keep their countdown line. (Armor already worked this way, talismans now match.)

🛠 Config

New keys are added to your talisman-bag block automatically. Your config, sets, talismans, and player data stay the same.

talisman-bag:
  prevent-duplicates: true   # block adding a talisman the bag already holds (false to allow copies)
  material: LIME_BUNDLE      # switch to a non-bundle (e.g. SHULKER_BOX) to silence the bundle sound

Run /zcg reload after any change.

📦 Install

Stop the server, replace the old jar with zCustomGear-2.5.0.jar, and start back up. Your config, sets, talismans, and player data are untouched.

📋 Version Breakdown

🎒 New: Talisman Bag

A new bag item lets players store their talismans in one tidy place. While the bag is anywhere in a player's inventory, every talisman kept inside still gives its bonus, just like carrying it in a normal slot, only neater.

• Easy to use: right-click the bag (or run /zcg bag while holding it) to open it, drag talismans in, and close. Bonuses turn on right away.
• Smart about contents: it only accepts normal talismans. Timer (countdown) talismans are blocked, since their timer only runs in a real inventory slot. Armor, swords, and other bags are turned away too, and any wrong item is handed straight back when the bag closes, so nothing is ever lost.
• Configurable: set the size (1 to 6 rows), the material and custom model data for a custom texture, and whether the bag and its contents survive death.

✨ Cleaner Look

The bag now uses a lime bundle look by default and shows a live list of the talismans kept inside, right on the item. Minecraft's own bundle text ("Can contain a stack...", "Empty") is hidden for you, replaced by a clean contents list that updates every time the bag is closed. You can still set any material you like, and the bundle text is hidden automatically for any bundle item.

⚡ Instant Effects

Talisman effects (speed, night vision, jump, and so on) now turn off the moment you remove the talisman, instead of slowly fading out over 30 seconds. Night vision no longer flickers, and while a talisman is carried its effect now shows as endless. Worn armor sets get the same treatment: no more flicker, and effects end the instant the set comes off.

🛠 Config

Both updates add their keys to your config.yml automatically under the talisman-bag block. Your sets, talismans, and player data stay exactly as they were.

talisman-bag:
  enabled: true
  title: "Talisman Bag"
  display-name: "&#44eebb&lTalisman Bag"
  material: LIME_BUNDLE
  custom-model- 0
  rows: 3
  keep-on-death: false
  contents-title: "&7Inside:"
  empty-text: "&8(empty)"

• rows bag size, 1 to 6 rows (9 slots each)
• material and custom-model-data set a custom texture
• keep-on-death set true to keep the bag and its contents on death
• contents-title header above the talisman list (set "" for none)
• empty-text the line shown when the bag is empty

Run /zcg reload after any change.

📦 Install

Stop the server, replace the old jar with zCustomGear-2.3.0.jar, and start back up. The new config keys are added for you, and your existing data is untouched.

📋 Version Breakdown

latest