Plugins | ✨LuckyBlocksPro [1.7 - 1.16.x]✨

Source: https://www.spigotmc.org/resources/%E2%9C%A8luckyblockspro-1-7-1-16-x-%E2%9C%A8-relaunch-sale.58438/

Tested Minecraft Versions:

1.7
1.8
1.9
1.10
1.11
1.12
1.13
1.14
1.15
1.16

This is a LuckyBlocks plugin. This plugin perfectly fits in any gamemodes ranging from factions and prisons to lobby and minigames. This is due to the fact that it's completely customizable. It has a very advanced, efficient, intuitive and adaptive configuration (luckyblocks.yml). You can customize everything and load as many different LuckyBlocks as you want.

Fully customizable (literally

)
Can run unlimited different LuckyBlocktypes at the same time
- Example: on your server, you have 3 different LuckyBlocks called "legendary", "epic" and "common". They can be made of different materials, have a different display name, different lore, different rewards...
No resource pack needed
Unlimited rewards and sub-rewards amount
Efficient rewards chance system
- chances are stored as doubles. Doubles can have up to 754 floating points
Ability to drop items and/or execute commands (with placeholders) and/or give potion effects and/or summon entities on LuckyBlocks opening
HeadDatabase integration (more than 20.000 custom heads)
Store placed LuckyBlocks locations using SQLite or YAML
Send and/or broadcast messages on LuckyBlocks opening
WorldGuard Integration
Ban system. Ability to prevent banned players from placing and opening LuckyBlocks
ParticlesEffects
Customizable date format
PlaceholderAPI integration
Limit LuckyBlocks usage to specific gamemodes (gamemodes whitelist)
Items found in LuckyBlocks naturally drops
Ability to set items durability and add ItemFlags
Multi-world support
Worlds blacklist (limit LuckyBlocks usage to specified worlds)
Bypass permissions
Info Item:
- In the config.yml you can set the "info item material" (default: golden nugget). You can see info about a placed LuckyBlock (like the data of the placing, who placed it, what type of LuckyBlock it is and the exact location) just by shifting+right-clicking it with an item of that material (the item must be in the off hand).
Ability to create skulls (you can use them as rewards and as LuckyBlock item) with custom textures
Extremely Lightweight
Eula friendly
Fast support
Support from 1.7 to 1.16.x
No dependencies!

See the configuration files for a more detailed explanation.
Available effects (this feature is in beta):

Spoiler: ParticlesEffects list

LuckyBlocks can be made of any block or skull. These are the default ones:

Spoiler: more

Default chat menus:

Help menu:

Status command output:

Info item interaction output:

/lbpro -> Main comman
/lbpro help -> Shows subcommands
/lbpro reload -> Reloads configuration files
/lbpro list-> List all LuckyBlocks types set in the configuration
/lbpro status -> Shows info about LuckyBlocks status
/lbpro ban <player> -> Prevent the player from placing and opening LuckyBlocks
/lbpro unban <player> -> Reallow the player to place and open LuckyBlocks
/lbpro banlist -> DIsplay all active bans
/lbpro get <type> <amount> -> Get n LuckyBlocks of that type
/lbpro give <player> <type> <amount> -> Give the player n LuckyBlocks of that type
/lbpro giveall <type> <amount> -> Give to all online players n LuckyBlocks of that type

Aliases: [/luckyblocks, /luckyblock, /lb, /lbpro, /lbp]

luckyblockspro.
- cmd.
  - reload -> Access to the reload command
  - list -> Access to the list command
  - status -> Access to the status command
  - ban -> Access to the ban command
  - unban -> Access to the unban command
  - banlist -> Access to the banlist command
  - get -> Access to the get command
  - give -> Access to the give command
  - giveall -> Access to the giveall command
- place -> Allows LuckyBlocks placing
- open -> Allows LuckyBlocks opening
- info -> Shows info about the LuckyBlocks while right-clicking them with the info item (see the config.yml for further info about this feature)
- bypass.
  - world -> Bypass blacklisted worlds restrictions
  - worldguard -> Bypass blacklisted WorldGuard regions restrictions
  - gamemode -> Bypass blocked gamemodes restrictions
- notify.update -> Get notified about updates

Note: underlined permissions are granted by default to all players

Default luckyblocks.yml:

Code (YAML):

# LuckyBlocks configuration file

# This is the type of the luckyblock. It's used internally by the plugin, players don't see it.
# NOTE: If you change the root section name all LuckyBlocks of that type placed before will not work
common:
# different LuckyBlocks CAN be of the same material
# NOTE: this has to be a block. Falling blocks (like SAND and GRAVEL) aren't fully supported yet.
material: PLAYER_HEAD # use SKULL_ITEM and uncomment "durability" for pre-1.13 servers
#durability: 3

# The skin of the head (This feature isn't available for 1.7 servers).
# The plugin supports two ways of setting the skin of the head:
# 1) Using textures from textures.minecraft.net
# 2) Using heads form HeadDatabase plugin (https://www.spigotmc.org/resources/14280/)

# Example 1
head-skin: http://textures.minecraft.net/textu...285afacb85eb8d0f79a5b46c5432d6feed66097c51248

# Example 2 (NOTE: the format is "hdb-ID", where ID is the head id)
# Don't forget to remove the # in front of the line
#head-skin: "hdb-25289"

# different LuckyBlocks CAN'T have the same name or lore
display-name: "&aCommon"
lore:
- "&bThis is a"
- "&bCommon LuckyBlock!"

# The rewards players may get by opening this LuckyBlock
rewards:
# The name of the reward (it's used internally, players can't see it)
# A reward is a container of sub-rewards (keep reading to find more info)
woolparty:
# The chance to get all the sub-rewards contained by this reward section
chance: 25

# But what is a sub-reward? There are four types of them: "drops", "commands", "potion-effects", and "summon-entities".
# A sub-reward must contain at least one of them

drops:
# This is a sub-reward! The section name (in this case "green") is used only internally,
# you can name it whatever you want. There can't be sections contained in the same parent-section
# with the same name (in this case only one of them would be loaded)
green:
# The only essential value is the material, the others are optional
material: GREEN_WOOL
# Item durability. The default value is 0, You can omit this:
durability: 0
display-name: "&2Green Wool"
lore:
- "&fThis is a &2green"
- "&fwool block"
# The default amount is 1, you can omit this
amount: 1
red:
material: RED_WOOL
#durability: 14
display-name: "&4Red Wool"
lore:
- "&fThis is a &4red"
- "&fwool block"
itemflags:
- "HIDE_ATTRIBUTES"
white:
material: WHITE_WOOL
display-name: "&fWhite Wool"
lore:
- "&fThis is a white"
- "&fwool block"
amount: 3

# There isn't a fixed amount of rewards and sub-rewards, you can add as many as you want

# This message is send to the player who get this reward (it's optional, you can omit it)
# {prefix} -> replaced with the chat prefix specified in the config.yml
message: "{prefix}&aYou found wool party!"

# Message broadcasted on LuckyBlock opening to all online players (it's optional, you can omit it)
# {player_name} -> replaced with the name of the player who opened the LuckyBlock
broadcast: "{prefix}&b{player_name} &6found wool party!"

# This is another reward
kit:
chance: 40
# Commands executed by the console
# Placeholders: {player_name}, {player_uuid}
commands:
- "kit tools {player_name}"

message: "{prefix}&aYou found a tools kit!"

# Another reward
stuff:
chance: 15
# Drop items
drops:
luckystone:
material: STONE
durability: 5
display-name: "&aLucky Stone"
lore:
- "&bThis is a"
- "&bLucky stone"
# Default amount is 1, you can omit this .....
amount: 2
luckywool:
material: RED_WOOL
display-name: "&aLucky Wool"
lore:
- "&aThis is a"
- "&aLucky wool"
amount: 4

# Another reward
spawncreeper:
chance: 10
summon-entities:
coolcreeper:
entity-type: CREEPER
# 1 by default, you can omit it
amount: 1
# You can omit the display name
display-name: "&bCool Creeper"
message: "{prefix}&aYou summoned a cool creeper!"

# Guess what? Another reward!
rank:
chance: 10
commands:
- "pex user {player_name} group add vip"

drops:
chestplate:
material: DIAMOND_CHESTPLATE
display-name: "&bVip Chestplate"
lore:
- "&bThis is a"
- "&bVip Chest"

# format: ENCHANTMENT_NAME:LEVEL
# https://hub.spigotmc.org/javadocs/spigot/org/bukkit/enchantments/Enchantment.html
enchantments:
- "DURABILITY:3"
- "PROTECTION_ENVIRONMENTAL:1"

broadcast: "{player_name} is now a vip player!"

# This is another LuckyBlock
epic:
material: PLAYER_HEAD
#durability: 3

enchantments:
- "DURABILITY:1"

itemflags:
- "HIDE_UNBREAKABLE"

head-skin: http://textures.minecraft.net/texture/6d0aac83e8ff2aada872b6437c96de9d5e58d55bcf979b298d2a64e3d84c8e
#head-skin: "hdb-11624" # Red LuckyBlock

display-name: "&5Epic"
lore:
- "&bThis is an"
- "&5Epic &bLuckyBlock!"
- ""
- "&7Place and break me"
- "&7to get awesome rewards!"

# I put random rewards, this is only an example. I don't suggest to use this LuckyBlock on a production server
rewards:
kit:
chance: 70
commands:
- "kit firework {player_name}"

message: "{prefix}&aYou found firework!"

preciousitems:
chance: 30

potion-effects:
bolt:
type: SPEED
# duration in seconds
duration: 30
level: 2

drops:
dia:
material: DIAMOND
lore:
- "&bPure diamonds!"
amount: 25
gold:
material: GOLD_INGOT
amount: 10
display-name: "&6Gold

"

message: "{prefix}&aYou're lucky man! This is precious stuff!"

# This is an example of a minimal configuration.
# It contains only necessary values
minimal-config-example:
material: SEA_LANTERN

display-name: "&3Basic Config LuckyBlock"

# Lore can be omitted but it's HIGHLY RECOMMENDED to use them to prevent players for abusing by duping LuckyBlocks
lore:
- "&bThis is a"
- "&aBasic configured &bLuckyBlock!"

rewards:
ore:
chance: 20
drops:
diamond:
material: DIAMOND_ORE
clay:
chance: 20
drops:
diamond:
material: CLAY
money:
chance: 50
commands:
- "eco give {player_name} 10"
cooleffect:
chance: 10
potion-effects:
regen:
type: REGENERATION
duration: 30
level: 3

Default config.yml:

Spoiler: config.yml

Requires PlaceholderAPI
Code (Text):
General placeholders:
%luckyblockspro_placed_amount% ➡ Amount of placed placeholders in the server
%luckyblockspro_types_amount% ➡ Amount of different LuckyBlock types configured in the luckyblocks.yml file
%luckyblockspro_rewards_amount% ➡ Amount of rewards configured in the luckyblocks.yml file
%luckyblockspro_subrewards_amount% ➡ Amount of subrewards configured in the luckyblocks.yml file
%luckyblockspro_infoitem_material% ➡ Capitalized info-item material (configured in the configuration file)
%luckyblockspro_bans_amount% ➡ Amount of banned players (banned by LBP)
%luckyblockspro_update_available% ➡ Whether there is an available plugin update

Players placeholders:
%luckyblockspro_is_banned% ➡ Whether the player is banned
%luckyblockspro_can_place% ➡ Whether the player has the permissions to place LuckyBlocks
%luckyblockspro_can_open% ➡ Whether the player has the permissions to open LuckyBlocks
%luckyblockspro_in_main_hand% ➡ Whether the player has a LuckyBlock in his main hand

true/false string values can be customized in the configuration file (config.yml) under the "Placeholders" section.
If you are using a MVdW plugin (like FeatherBoard) you can use different placeholders:
Code (Text):
{placeholderapi_*}

* = placeholder without '%'

Example:
{placeholderapi_luckyblockspro_bans_amount}