Added Survival Plugin Configuration

survival/plugins/ChestShop/config.yml

@@ -0,0 +1,190 @@
+# Should the plugin log some messages that are useful for debugging?
+DEBUG: false
+
+# Do you want to turn off the automatic updates of ChestShop?
+TURN_OFF_UPDATES: true
+# Do you want to turn off the automatic notifications for new development builds?
+TURN_OFF_DEV_UPDATE_NOTIFIER: false
+# Do you want to include some values of this config in the metrics? (This will not leak sensitive data but help in the development process)
+INCLUDE_SETTINGS_IN_METRICS: true
+
+# How large should the internal caches be?
+CACHE_SIZE: 1000
+
+# The default language when the client's language can't be found.
+DEFAULT_LANGUAGE: "en"
+# Should the plugin try to use a language file that matches the client's locale setting?
+USE_CLIENT_LOCALE: true
+
+# What containers are allowed to hold a shop? (Only blocks with inventories work!)
+SHOP_CONTAINERS:
+- "CHEST"
+- "TRAPPED_CHEST"
+- "BARREL"
+- "SHULKER_BOX"
+- "WHITE_SHULKER_BOX"
+- "ORANGE_SHULKER_BOX"
+- "MAGENTA_SHULKER_BOX"
+- "LIGHT_BLUE_SHULKER_BOX"
+- "YELLOW_SHULKER_BOX"
+- "LIME_SHULKER_BOX"
+- "PINK_SHULKER_BOX"
+- "GRAY_SHULKER_BOX"
+- "LIGHT_GRAY_SHULKER_BOX"
+- "CYAN_SHULKER_BOX"
+- "PURPLE_SHULKER_BOX"
+- "BLUE_SHULKER_BOX"
+- "BROWN_SHULKER_BOX"
+- "GREEN_SHULKER_BOX"
+- "RED_SHULKER_BOX"
+- "BLACK_SHULKER_BOX"
+
+# (In 1/1000th of a second) How often can a player use the shop sign?
+SHOP_INTERACTION_INTERVAL: 250
+# Do you want to block people in creative mode from using shops?
+IGNORE_CREATIVE_MODE: true
+# Do you want to block people who have access to a shop due to their permissions from using it? (owners are always ignored)
+IGNORE_ACCESS_PERMS: true
+# If true, people will buy with left-click and sell with right-click.
+REVERSE_BUTTONS: false
+# If true, people will be able to buy/sell in 64 stacks while holding the crouch button.
+SHIFT_SELLS_IN_STACKS: false
+# If true, people will be able to sell/buy everything available of the same type.
+SHIFT_SELLS_EVERYTHING: false
+# What can you do by clicking shift with SHIFT_SELLS_IN_STACKS turned on? (ALL/BUY/SELL)
+SHIFT_ALLOWS: "ALL"
+# Can shop's chest be opened by owner with right-clicking a shop's sign?
+ALLOW_SIGN_CHEST_OPEN: false
+# If true, when you left-click your own shop sign you won't open chest's inventory, but instead you will start destroying the sign.
+ALLOW_LEFT_CLICK_DESTROYING: true
+
+# If true, if the shop is empty, the sign is destroyed and put into the chest, so the shop isn't usable anymore.
+REMOVE_EMPTY_SHOPS: false
+# If true, if the REMOVE_EMPTY_SHOPS option is turned on, the chest is also destroyed.
+REMOVE_EMPTY_CHESTS: false
+# A list of worlds in which to remove empty shops with the previous config. Case sensitive. An empty list means all worlds.
+REMOVE_EMPTY_WORLDS:
+- "world1"
+- "world2"
+
+# First line of your Admin Shop's sign should look like this:
+ADMIN_SHOP_NAME: "Admin Shop"
+# Make all admin shops be unlimited even if they have a shop container at the sign
+FORCE_UNLIMITED_ADMIN_SHOP: false
+# The name of the economy account which Admin Shops should use and to which all taxes will go
+SERVER_ECONOMY_ACCOUNT: ""
+# The uuid of the economy account for the Admin Shop. Useful for fake accounts as normally only accounts of players work
+SERVER_ECONOMY_ACCOUNT_UUID: 00000000-0000-0000-0000-000000000000
+# Percent of the price that should go to the server's account. (100 = 100 percent)
+TAX_AMOUNT: 0
+# Percent of the price that should go to the server's account when buying from an Admin Shop.
+SERVER_TAX_AMOUNT: 0
+# Amount of money player must pay to create a shop
+SHOP_CREATION_PRICE: 0
+# How much money do you get back when destroying a sign?
+SHOP_REFUND_PRICE: 0
+# How many decimal places are allowed at a maximum for prices?
+PRICE_PRECISION: 2
+# This makes sure that the UUIDs of player shop accounts match the server's online-mode setting. Disabling this might lead to issues with offline players and is therefore unsupported!
+ENSURE_CORRECT_PLAYERID: true
+# This regexp validates the name of the player. If the name doesn't match, the player will neither be able to create a valid shop sign, nor buy/sell from a shop.
+# Note for Bedrock support: If you have Floodgate on your server, you should set this regexp to ^\\*?\\w+$ and ENSURE_CORRECT_PLAYERID to false
+# If your Floodgate prefix is not *, change the first * in the regexp (the one before the question mark) to whatever your prefix is.
+VALID_PLAYERNAME_REGEXP: "^\\.?\\w+$"
+
+# Should we block shops that sell things for more than they buy? (This prevents newbies from creating shops that would be exploited)
+BLOCK_SHOPS_WITH_SELL_PRICE_HIGHER_THAN_BUY_PRICE: true
+
+# Maximum amount of items that can be bought/sold at a shop. Default 3456 is a double chest of 64 stacks.
+MAX_SHOP_AMOUNT: 3456
+
+# Do you want to allow other players to build a shop on a block where there's one already?
+ALLOW_MULTIPLE_SHOPS_AT_ONE_BLOCK: false
+# Can shops be used even when the buyer/seller doesn't have enough items, space or money? (The price will be scaled adequately to the item amount)
+ALLOW_PARTIAL_TRANSACTIONS: true
+# Can '?' be put in place of item name in order for the sign to be auto-filled?
+ALLOW_AUTO_ITEM_FILL: true
+
+# Enable this if you use BungeeCord and want players to receive shop notifications on other servers
+BUNGEECORD_MESSAGES: false
+
+# Do you want to show "Out of stock" messages?
+SHOW_MESSAGE_OUT_OF_STOCK: true
+# Do you want to show "Full shop" messages?
+SHOW_MESSAGE_FULL_SHOP: true
+# How many seconds do you want to wait before showing notifications for the same shop to the owner again?
+NOTIFICATION_MESSAGE_COOLDOWN: 10
+
+# Can players hide the "Out of stock" messages with /cstoggle?
+CSTOGGLE_TOGGLES_OUT_OF_STOCK: false
+# Can players hide the "Full shop" messages with /cstoggle?
+CSTOGGLE_TOGGLES_FULL_SHOP: false
+# Do you want to show "You bought/sold... " messages?
+SHOW_TRANSACTION_INFORMATION_CLIENT: true
+# Do you want to show "Somebody bought/sold... " messages?
+SHOW_TRANSACTION_INFORMATION_OWNER: true
+
+# If true, plugin will log transactions in its own file
+LOG_TO_FILE: false
+# Do you want ChestShop's messages to show up in console?
+LOG_TO_CONSOLE: true
+# Should all shop removals be logged to the console?
+LOG_ALL_SHOP_REMOVALS: true
+
+# Do you want to stack all items up to 64 item stacks?
+STACK_TO_64: false
+# Do you want to use built-in protection against chest destruction?
+USE_BUILT_IN_PROTECTION: true
+# Do you want to have shop signs "stick" to chests?
+STICK_SIGNS_TO_CHESTS: false
+# EXPERIMENTAL: Do you want to turn off the default protection when another plugin is protecting the block? (Will leave the chest visually open - CraftBukkit bug!)
+TURN_OFF_DEFAULT_PROTECTION_WHEN_PROTECTED_EXTERNALLY: false
+# Do you want to turn off the default sign protection? Warning! Other players will be able to destroy other people's shops!
+TURN_OFF_SIGN_PROTECTION: false
+# Do you want to disable the hopper protection, which prevents Hopper-Minecarts from taking items out of shops?
+TURN_OFF_HOPPER_PROTECTION: false
+# Only allow users to buy/sell that have access to the sign's protection? (E.g. LWC protection)
+CHECK_ACCESS_FOR_SHOP_USE: false
+# Do you want to protect shop chests with LWC?
+PROTECT_CHEST_WITH_LWC: false
+# Of which type should the container protection be? Possible type: public, private, donate and on some LWC versions display
+LWC_CHEST_PROTECTION_TYPE: "PRIVATE"
+# Do you want to protect shop signs with LWC?
+PROTECT_SIGN_WITH_LWC: false
+# Of which type should the sign protection be? Possible type: public, private, donate and on some LWC versions display
+LWC_SIGN_PROTECTION_TYPE: "PRIVATE"
+# Should the chest's LWC protection be removed once the shop sign is destroyed?
+REMOVE_LWC_PROTECTION_AUTOMATICALLY: true
+# Should LWC limits block shop creations?
+LWC_LIMITS_BLOCK_CREATION: true
+
+# Do you want to only let people build inside WorldGuard regions?
+WORLDGUARD_INTEGRATION: false
+# Do you want to only let people build inside region flagged by doing /region regionName flag allow-shop allow?
+WORLDGUARD_USE_FLAG: false
+# Do you want ChestShop to respect WorldGuard's chest protection?
+WORLDGUARD_USE_PROTECTION: false
+
+# Do you want to only let people build inside GriefPrevention claims?
+GRIEFPREVENTION_INTEGRATION: false
+
+# Do you want to only let people build inside RedProtect regions?
+REDPROTECT_INTEGRATION: false
+
+# Do you want to deny shop access to unlogged users?
+AUTHME_HOOK: true
+# Do you want to allow shop access to unregistered users? (Example: registration is optional)
+AUTHME_ALLOW_UNREGISTERED: false
+
+# How much Heroes exp should people get for creating a ChestShop?
+HEROES_EXP: 100.0
+
+# Add icons and make item names hoverable in transaction messages when ShowItem is installed?
+SHOWITEM_MESSAGE: true
+
+# Add stock counter to quantity line?
+USE_STOCK_COUNTER: false
+
+# If true and in 1.14+, the owner of a chest shop can click with a dye / ink sac to dye the sign.
+SIGN_DYING: true
+

survival/plugins/ChestShop/discounts.yml

@@ -0,0 +1,7 @@
+# This file is for discount management. You are able to do that:
+# group1: 75
+# That means that the person with ChestShop.discount.group1 permission will pay only 75% of the price. 
+# For example, if the price is 100 dollars, the player pays only 75 dollars.
+# (Only works in buy-only Admin Shops!)
+
+{}

survival/plugins/ChestShop/itemAliases.yml

@@ -0,0 +1,4 @@
+# This file specified optional aliases for certain item codes. (Use the full name from /iteminfo)
+# Please note that these aliases should fit on a sign for it to work properly!
+Item String#3d: My Cool Item
+Other Material#Eg: Some other Item

survival/plugins/ChestShop/jenkinsBuildsNotifier.yml

@@ -0,0 +1,3 @@
+disabled: false
+jenkins-job-url-override: ''
+last-announced-build: 363

survival/plugins/ChestShop/priceLimits.yml

@@ -0,0 +1,13 @@
+# In this file you can configure maximum and minimum prices for items (when creating a shop).
+uses_materials: true
+max:
+  buy_price:
+    item_type: 5.53
+    piston_head: 3.51
+  sell_price:
+    placed_banner: 3.52
+min:
+  buy_price:
+    piston_head: 1.03
+  sell_price:
+    placed_banner: 0.51

survival/plugins/ChestShop/version

@@ -0,0 +1,2 @@
+version: 4
+metadata-version: 3120

survival/plugins/Chunky/config.yml

@@ -0,0 +1,19 @@
+# Chunky Configuration
+# https://github.com/pop4959/Chunky/wiki/Configuration
+
+force-load-existing-chunks: false
+version: 1
+language: en
+continue-on-restart: false
+silent: false
+update-interval: 1
+tasks:
+  world:
+    cancelled: true
+    radius: 1000.0
+    x-center: 2252.0
+    z-center: 3845.0
+    iterator: concentric
+    shape: square
+    count: 16129
+    time: 1971399

survival/plugins/DailyRewards/config.yml

@@ -0,0 +1,71 @@
+# PlaceholderAPI
+# Version: 2.10.9
+# Created by: extended_clip
+# Contributors: https://github.com/PlaceholderAPI/PlaceholderAPI/graphs/contributors
+# Issues: https://github.com/PlaceholderAPI/PlaceholderAPI/issues
+# Expansions: https://api.extendedclip.com/all/
+# Wiki: https://github.com/PlaceholderAPI/PlaceholderAPI/wiki
+# Discord: https://helpch.at/discord
+# No placeholders are provided with this plugin by default.
+# Download placeholders: /papi ecloud
+check_updates: true
+cloud_enabled: true
+cloud_sorting: name
+cloud_allow_unverified_expansions: false
+boolean:
+  'true': 'yes'
+  'false': 'no'
+date_format: MM/dd/yy HH:mm:ss
+debug: false
+cooldown: 86400000
+savetoip: false
+regenerate-default-rewards: false
+mysql:
+  enabled: false
+  host-name: mc-database
+  port: 3306
+  database: rewards
+  username: rewardsuser
+  password: change-me-password-rewards-db
+loginclaim:
+  enabled: false
+  delay: 3
+claim:
+  sound:
+    enabled: true
+    type: ENTITY_PLAYER_LEVELUP
+    volume: 1
+    pitch: 1
+noreward:
+  sound:
+    enabled: true
+    type: BLOCK_ANVIL_LAND
+    volume: 1
+    pitch: 1
+rewards:
+  basic:
+    name: Basic
+    permission: true
+    random: false
+    claim-message: '&aRewards&f: You claimed the &7Basic&f Daily Reward!'
+    broadcast: ''
+    commands:
+    - give %player minecraft:diamond 1
+  advanced:
+    name: Advanced
+    permission: true
+    random: true
+    claim-message: ''
+    broadcast: '&aRewards&f: %player claimed the &eAdvanced&f Daily Reward!'
+    commands:
+    - give %player minecraft:diamond 1;say %player earned a common diamond
+    - give %player minecraft:diamond 1;say %player earned a common diamond
+    - give %player minecraft:emerald 1;say %player earned a rare emerald
+  player:
+    name: UserReward
+    permission: false
+    random: false
+    claim-message: '&aRewards&f: You claimed your Daily Reward!'
+    broadcast: ''
+    commands:
+    - eco %player give 10

survival/plugins/DailyRewards/messages.yml

@@ -0,0 +1,8 @@
+no-rewards: '&aRewards&f: &fYou do not have any available rewards at the moment.'
+cooldown-msg: '&aRewards&f: &fTime until next reward: %time%'
+no-permission: '&aRewards&f: &fYou do not have permission to do '
+reward-available: '&aRewards&f: &fYou have unclaimed daily rewards, do &e/reward &fto
+  claim!'
+PlaceholderAPI:
+  reward-available: Unclaimed Rewards Available!
+  no-rewards: No Rewards Available

survival/plugins/LuckPerms/config.yml

@@ -83,7 +83,7 @@ use-server-uuid-cache: false
 #
 # - A H2 database is the default option.
 # - If you want to edit data manually in "traditional" storage files, we suggest using YAML.
-storage-method: h2
+storage-method: MariaDB
 
 # The following block defines the settings for remote database storage methods.
 #
@@ -99,11 +99,11 @@ data:
 
   # The name of the database to store LuckPerms data in.
   # - This must be created already. Don't worry about this setting if you're using MongoDB.
-  database: minecraft
+  database: permission
 
   # Credentials for the database.
-  username: root
-  password: ''
+  username: luckperms
+  password: 'change-me-password-luckperms-db'
 
   # These settings apply to the MySQL connection pool.
   # - The default values will be suitable for the majority of users.