Destroy The Core - [1.8-1.15] 1.0.8

Players battle to destroy a core to receive rewards!
Destroy The Core [1.8-1.15]
Players battle to destroy a core and receive rewards

features.png
  • Fun lightweight PvP-based Event
  • Simple Setup Process
  • Easily setup automatic events with /dtc schedule.
  • Leaderboard of Top Event Winners (/dtc top)
  • Easily Set a Core By Looking at The Block
  • Each core has different rewards (configurable in cores.yml)
commands.png
  • /dtc create <core name> <life> - Creates a core
  • /dtc remove <name>- Removes a core
  • /dtc list - Lists all available cores
  • /dtc start <core name> - Starts a core
  • /dtc stop <core name> - Stops a core
  • /dtc info <core name> - Shows a core's info (status, coordinates, top players)
  • /dtc tp <core name> - Teleport to the core
  • /dtc setmaxlife <core name> - Updates the core's max life
  • /dtc top - Lists the top event winners
  • /dtc schedule <core> <time> - Setup an automatic event
  • /dtc listschedule - Lists all scheduled cores
  • /dtc reload - Reloads the config.yml and cores.yml
permissions.png
  • dtc.help - Permission to use /dtc and /dtc help
  • dtc.create - Permission to use /dtc create
  • dtc.remove - Permission to use /dtc remove
  • dtc.list - Permission to use /dtc list
  • dtc.start - Permission to use /dtc start
  • dtc.stop- Permission to use /dtc stop
  • dtc.info - Permission to use /dtc info
  • dtc.tp - Permission to use /dtc tp
  • dtc.setmaxlife - Permission to use /dtc setmaxlife
  • dtc.top - Permission to use /dtc top
  • dtc.schedule - Permission to use /dtc schedule
  • dtc.listschedule - Permission to use /dtc listschedule
  • dtc.next - Permission to use /dtc next
  • dtc.reload - Permission to use /dtc reload
placeholders.png

HolographicDisplays
{dtc_top_1}
- Gets the 1st place player on /dtc top
{dtc_top_2} - Gets the 2nd place player on /dtc top
{dtc_top_3} - Gets the 3rd place player on /dtc top
{dtc_next_name} - Gets the name of the next scheduled core
{dtc_next_time} - Gets the time until the next scheduled core


PlaceholderAPI
%dtc_current_name%
- Gets the name of the active core
%dtc_current_coords% - Gets the coordinates of the active core
%dtc_next_name% - Gets the name of the next scheduled core
%dtc_next_time% - Gets the time until the next scheduled core
%dtc_current_players_1% - Gets the player with the most points for the current core
%dtc_current_players_2% - Gets the second player with the most points for the current core
%dtc_current_players_3% - Gets the third player with the most points for the current core
showcase.png


configuration.png

Code:
# DestroyTheCore created by Dreewww

############################################################
# +------------------------------------------------------+ #
# |                       General                        | #
# +------------------------------------------------------+ #
############################################################
prefix: '&4&lDTC &7┃ '
must-be-player: '&cMust be a player to run this command'
no-permission: '&cNo Permission'
reload: '&aConfig.yml & Cores.yml Successfully Reloaded!'
help:
  - ''
  - '&4&lDestroy The Core'
  - '&7/dtc create <name> <life> &7- &fCreates a core'
  - '&7/dtc remove <name> &7- &fRemoves a core'
  - '&7/dtc list &7- &fLists all cores'
  - '&7/dtc start <name> &7- &fStarts a core'
  - '&7/dtc stop <name> &7- &fStops a core'
  - '&7/dtc info <name> &7- &fLists a cores''s info'
  - '&7/dtc tp <name> &7- &fTeleport to the core'
  - '&7/dtc top &7- &fLists top event winners'
  - '&7/dtc schedule <name> <time> &7- &fSchedules a core'
  - '&7/dtc listschedule &7- &fLists all scheduled cores'
  - '&7/dtc next &7- &fShows when the next core starts'
  - ''
core-none-exist: '&cThere are no available cores.'
core-doesnt-exist: '&cThe core %CORE% doesn''t exist!'
core-not-running: '&cThe %CORE% core isn''t running!'
core-already-running: '&cThe core %CORE% is already running!'
core-another-running: '&cThere is already another active core.'
core-block-broken: '&c%PLAYER% &7has broken a piece of &c%CORE% &8(&c%CURRENT_LIFE%&7/&c%MAX_LIFE%&8)'
core-win-message: '&c%PLAYER% &7has destroyed the &c%CORE% &7core!'
core-inactive-stop: '&cThe %CORE% core has stopped due to nobody breaking it.'

############################################################
# +------------------------------------------------------+ #
# |                   /dtc create                        | #
# +------------------------------------------------------+ #
############################################################

# Which blocks should be set as a Core?
materials:
  - 'OBSIDIAN'
create-usage: '&7/dtc create <name> <life>'
create-block-doesnt-exist: '&cPlease look at the block that you want to set as the core!'
create-invalid-life: '&cPlease provide a valid number for the core''s life.'
create-core-exists: '&cThe core %CORE% already exists!'
create-location-exists: '&cThere is already a core set at this location.'
create-invalid-material: '&c%MATERIAL% isn''t listed as an available core block in the config.'
create-success: '&7Successfully created the &a%CORE% &7core at &c%LOCATION% &8(&a%LIFE% hits&8)'

############################################################
# +------------------------------------------------------+ #
# |                   /dtc remove                        | #
# +------------------------------------------------------+ #
############################################################
remove-usage: '&7/dtc remove <name>'
remove-success: '&7Successfully removed the &c%CORE% &7core.'

############################################################
# +------------------------------------------------------+ #
# |                    /dtc list                         | #
# +------------------------------------------------------+ #
############################################################
list-values: '&c#%NUMBER%. &c%NAME% &7- &7%LOCATION%'
list-success:
  - ''
  - '&4&lAvailable Cores'
  - ''
  - '%VALUES%'
  - ''

############################################################
# +------------------------------------------------------+ #
# |                  /dtc start                          | #
# +------------------------------------------------------+ #
############################################################
start-usage: '&7/dtc start <name>'
start-success:
    - ''
    - '                           &4&lDestroy The Core'
    - '                     &7The %CORE% Core has begun!'
    - '              &7Run &c/dtc info %CORE% &7for more info.'
    - ''

############################################################
# +------------------------------------------------------+ #
# |                  /dtc stop                           | #
# +------------------------------------------------------+ #
############################################################
stop-usage: '&7/dtc stop <name>'
stop-success: '&c%PLAYER% &7has stopped the &c%CORE% &7core.'

############################################################
# +------------------------------------------------------+ #
# |                  /dtc info                           | #
# +------------------------------------------------------+ #
############################################################
info-usage: '&7/dtc info <name>'
info-values: '&8[&4&l%POSITION%&8] &c%PLAYER_NAME% &8(&c%POINTS%&7/&c%LIFE%&8)'
info-success:
  - ''
  - '&4&l%CORE% Core'
  - '&7Status: &f%STATUS%'
  - '&7Location: &f%LOCATION%'
  - '&7Top Players: '
  - ''
  - '%VALUES%'

############################################################
# +------------------------------------------------------+ #
# |                   /dtc top                           | #
# +------------------------------------------------------+ #
############################################################
top:
  no-results: '&7There arent any Core Win results.'
  values: '&8[&4&l%POSITION%&8] &c%PLAYER_NAME% &7- %WINS%'
  results:
    - '&8&m----------------------------------------------------'
    - '&4&lCore Wins'
    - ''
    - '%VALUES%'
    - ''
    - '&8&m----------------------------------------------------'

############################################################
# +------------------------------------------------------+ #
# |                   /dtc tp                            | #
# +------------------------------------------------------+ #
############################################################
tp-usage: '&7/dtc tp <name>'
tp-success: '&7Successfully teleported to the &c%CORE% &7core.'

############################################################
# +------------------------------------------------------+ #
# |                /dtc setmaxlife                       | #
# +------------------------------------------------------+ #
############################################################
set-max-life-usage: '&7/dtc setmaxlife <core> <number>'
set-max-life-core-is-active: '&cYou cannot edit an active core.'
set-max-life-success: '&7Successfully set &c%CORE%''s &7life to &c%LIFE%&7.'

############################################################
# +------------------------------------------------------+ #
# |                 /dtc schedule                        | #
# +------------------------------------------------------+ #
############################################################
schedule-usage:
  - ''
  - '&4&lScheduling a Core'
  - ''
  - '&7/dtc schedule <core> <time>'
  - '&7Current Time: &f%CURRENT_TIME%'
  - ''
  - '&4Note: &7Make sure to include a &8"&7:&8" &7to separate the'
  - '&7hour from the minute and &8"&7am/pm&8"'
  - ''
  - '&4&lExamples'
  - '&8» &c/dtc schedule Core1 12:00am'
  - '&8» &c/dtc schedule Core1 3:00pm'
schedule-invalid-time: '&cPlease enter a valid time &8(&cie: "21:00"&8)'
schedule-invalid-hour: '&cPlease enter a valid hour &8(&cie: 0-24&8)'
schedule-invalid-minute: '&cPlease enter a valid minute &8(&cie: 00-59&8)'
schedule-success: '&c%CORE% &7core &7will now start at &c%TIME%&7.'

############################################################
# +------------------------------------------------------+ #
# |               /dtc listschedule                      | #
# +------------------------------------------------------+ #
############################################################
list-schedule-none: '&cThere are no scheduled cores.'
list-schedule-values: '&8» &c%TIME% &7- %CORE%'
list-schedule-success:
  - ''
  - '&4&lScheduled Cores'
  - ''
  - '%VALUES%'
  - ''

############################################################
# +------------------------------------------------------+ #
# |                  /dtc next                           | #
# +------------------------------------------------------+ #
############################################################
next-success: '&7The next core &c%CORE% &7will start in &c%TIME%'

Need Support? Please join my Discord server by clicking the logo above or use this link: https://discord.gg/88ekwP6.

Latest updates

  1. 1.0.8

    Hologram placeholders should now automatically reload Added new PlaceholderAPI placeholders...
  2. 1.0.7

    Fixed an error with /dtc next when no cores were scheduled Fixed an error with placeholders when...
  3. 1.0.6

    Added the ability to change the scheduler timezone. Add this section to your config.yml...

Latest reviews

Amazing plugin made by a high quality developer. Everything Andrew makes is tested thoroughly and optimized with high player counts in mind. Support is also top notch -- he responds to any requests or issues quickly via Discord. Major vouch.
Nice plugin, works as described.
Anndrew
Anndrew
thank you for the review ;)
Top
You need to upgrade!
Our dark style is reserved for our Premium members. Upgrade here.