TierRequirements
Scorpion edited this page 5 years ago

This page is dedicated to V2.x.x+ requirements. For a starting guide(specially upgrading from 1.x.x) Click here

Disclaimer: This page is still a WIP

The following plugins/sections are supported:

  • mcmmo
  • bcgems
  • jobs reborn
  • placeholderapi
  • quests
  • votifier
  • nuvotifier
  • mmocore
  • playerpoints
  • skillapi
  • vault
  • mcrpg
  • player
  • playerstatistics
  • advancements

    permissions:
    bcranks.setitem:
    description: Set the gui Items
    default: op
    bcranks.update.notify:
    description: be notified on updates
    default: op
    bcranks.add:
    description: Add tier + rank to a players status
    default: op
    bcranks.convert:
    description: Convert the settings.yml to tier.yml settings
    default: false
    bcranks.reload:
    description: Reload the settings
    default: op
    
    Commands:
    main: bcranks
    Alias: bcr | bcrank
    - add (player) (tier) (rank)
    - open (custom/timed/tiers/(tier name)
    - convert
    - reload
    - setitem (connect/timed/custom/placeholder)
    

Unlike the settings.yml which requires:

Requirements:
  mcmmo:
  - 'woodcutting'
  - 'mining'
  mcmmocombined: 30
  

Tiers have been made completely customizable per section/skill/rank you name it. Similar to the above example you dont need to "combine" the skill level and instead:

Requirements:
- 'mcmmo;woodcutting;30;Reached %s Woodcutting;Reach %s woodcutting. Now: %current%'
- 'mcmmo;mining;30;Reached %s Mining;Reach %s mining. Now: %current%'

As you can see, not much has changed but you can change the order and make mcmmo skills level unique. This goes for every section. Every page(i.e this) is still valid. The only difference(as per linked page)

Instead of using: 'points:20:Obtained %s points!:Required; %s points. Current; %current%'

You use:

'mcrpg;points:20:Obtained %s points!:Required; %s points. Current; %current%'