TMDevelopmentTinulica & Maiky

Kill milestones

(4.2.0+) A milestone gives rewards when a player reaches a number of kills. Every milestone is given once. Everything is in milestones.yml; the menu that shows the progress is menus/milestones.yml.

Milestones are off on a new install and on servers that update: turn them on with enabled: true in milestones.yml (then /mobcoins reload) or with the Kill milestones button in /mobcoins settings.

Example

enabled: true

milestones:
  kills-100:                 # the id: it is what is saved, renaming it gives the milestone again
    kills: 100               # kills needed
    name: "&#f7c948Hunter"
    item: "IRON_SWORD"       # icon in the menu
    description: "&7Reward: &#f7c948100 mobcoins"
    rewards:
      - "[mobcoins_give] 100"
      - "[title] &#f7c948Milestone!;&7100 kills"
      - "[sound] ENTITY_PLAYER_LEVELUP"
  kills-1000:
    kills: 1000
    name: "&#f7c948Legend"
    item: "DIAMOND_SWORD"
    description: "&7Reward: &#f7c9481,000 mobcoins + x2 booster (30m)"
    rewards:
      - "[mobcoins_give] 1000"
      - "[console] mobcoins booster give {player} 2 30m"
  zombies-250:
    kills: 250
    mobs: [ZOMBIE, HUSK, DROWNED, ZOMBIE_VILLAGER]   # only these mobs count
    name: "&#f7c948Zombie hunter"
    item: "ROTTEN_FLESH"
    rewards:
      - "[mobcoins_give] 250"
Option
killskills needed. Every mob killed by the player counts: the same number as /mobcoins stats
mob / mobsonly the kills of these mobs count (ZOMBIE or a list). MythicMobs: mythic:SkeletonKing
nameshown in the menu and in the messages (FlareMobCoins)
itemicon in the menu: a material, head:Notch or texture:<value>. Empty = PAPER
descriptionone line in the menu ({description}), e.g. what the player gets
rewardsthe same actions as the shops: [mobcoins_give], [console], [player], [message], [broadcast], [title], [actionbar], [sound], [tokens_give], [money_give] ... Placeholders: {player} FlareMobCoins {required} {kills}
  • Players who already have the kills (for example when you turn milestones on) get the milestone at their next kill.
  • The reached milestones are saved with the stats: with MySQL they are the same on every server of the network.
  • /mobcoins milestones reset <player> gives the milestones again: at his next kill the player gets every milestone he already has the kills for (useful to test the rewards).
  • Ids are simple words like kills-100: no dots, and not on, off, yes or no.

Messages

In lang/en.yml > milestones:

milestones:
  reached:
    - "{prefix}&7Milestone &#f7c948FlareMobCoins &7reached &8({required} kills)&7!"
  broadcast: ""   # e.g. "{prefix}&f{player} &7reached the milestone &#f7c948FlareMobCoins&7!"

broadcast is off (""); write a text to tell everybody. Like every message, they can also go to the title or the action bar: see Colors and text format.

/mobcoins milestones opens menus/milestones.yml: one slot per milestone, the kills, a progress bar and Reached! (reached ones glow). More milestones than slots = pages with the arrows. Change it like the other menus with /mobcoins editor milestones. Placeholders of the entries: FlareMobCoins {kills} {required} {progress} (0-100) {bar} {status} {description}.

To open it from the main menu, add a button with the action [open] milestones.

Commands and permissions

CommandPermissionDefault
/mobcoins milestonesflaremobcoins.command.milestoneseveryone
/mobcoins milestones <player>flaremobcoins.command.milestones.otherop
/mobcoins milestones reset <player>flaremobcoins.command.milestones.resetop

Normal players can be kept out with player-access.milestones: false in config.yml.

Placeholders

%flaremobcoins_milestones_reached% · %flaremobcoins_milestones_total% · %flaremobcoins_milestone_next% (name of the closest one) · %flaremobcoins_milestone_next_kills% · %flaremobcoins_milestone_next_required% · %flaremobcoins_milestone_next_progress% (0-100)

Last updated

Sign in

New here? Just enter your email: the account is created when you click the link. No password needed.

or

We send you a link that signs you in with one click. It works for new and existing accounts.

Sign in with a password instead

By continuing you accept the Terms & Conditions and the Privacy policy.

Staff: open “Sign in with a password instead” and type your username instead of the email. After the password we ask for your 2FA code.