Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicDungeons MythicDungeons
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 90
    • Issues 90
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicDungeonsMythicDungeons
  • Wiki
  • Dungeon Config

Dungeon Config · Changes

Page history
Create Dungeon Config authored Jun 08, 2022 by MarcatoSound's avatar MarcatoSound
Hide whitespace changes
Inline Side-by-side
Showing with 79 additions and 0 deletions
+79 -0
  • Dungeon-Config.md Dungeon-Config.md +79 -0
  • No files found.
Dungeon-Config.md 0 → 100644
View page @ f6a6ccd9
Every dungeon has its own unique config file that lets you further customize the dungeon's behaviour when played. This includes entry requirements, blocking certain potential out-of-bounds abuse (enderpearls, chorus fruit, etc), and reward cooldowns.
_An in-game editor for this config is planned for the future, but for now, you'll have to manually edit the config file._
NOTE: Gamerules are stored on the map itself and can be edited in-game with the standard /gamerule command.
```yml
General:
# Do not change! Used to track the config version when major updates happen.
Version: 1
DisplayName: "&bA Dungeon"
Lobby:
Enabled: true
Gamemode: SURVIVAL
PlayerLives: 0
KeepInventoryOnEnter: true
KickOfflinePlayers: true
KickOfflinePlayersDelay: 300
MaxBackups: 7
# Loot Cooldown makes it so that players can't loot chests they've already looted recently.
# Reward functions can be configured individually, or use the default values provided in this section.
LootCooldown:
Enabled: false
# Whether or not the cooldown is per-chest or dungeon-wide. !!NOT CURRENTLY WORKING!!
PerReward: true
# Setting this to TIMER will make it so the player can't get loot again until their cooldown is up.
# Options like HOURLY, DAILY, WEEKLY, and MONTHLY will let you configure a set time for loot to be reset.
CooldownType: DAILY
# If type is set to TIMER, this is how many minutes until the player can acquire loot again.
# Otherwise, this is the time of day when the reset occurs in hours.
CooldownTime: 0
# If type is set to WEEKLY, ResetDay determines what numbered day of the week the reset occurs.
# "Sunday" would be 1, "Monday" is 2, "Tuesday" is 3, etc.
# If type is set to MONTHLY, ResetDay determines what day of the month the reset occurs.
# Doesn't do anything if CooldownType is set to "TIMER"
ResetDay: 1
# Access cooldown is used to limit how quickly a player can play this dungeon again after playing it.
# NOTE: Be wary using this, as this can result in players being unable to play with each other if one of them has already run the dungeon recently!
# The "LootCooldown" section should be used instead to avoid this.
AccessCooldown:
Enabled: false
# Setting this to TIMER will make it so the player can't get run this dungeon again until their cooldown is up.
# Options like HOURLY, DAILY, WEEKLY, and MONTHLY will let you configure a set time for access to be reset.
CooldownType: DAILY
# If type is set to TIMER, this is how many minutes until the player can player the dungeon again.
# Otherwise, this is the time of day when the reset occurs in hours.
CooldownTime: 0
# If type is set to WEEKLY, ResetDay determines what numbered day of the week the reset occurs.
# "Sunday" would be 1, "Monday" is 2, "Tuesday" is 3, etc.
# If type is set to MONTHLY, ResetDay determines what day of the month the reset occurs.
ResetDay: 1
Requirements:
# A list of permissions the player must have.
Permissions: []
MinPartySize: 1
MaxPartySize: 4
# A list of dungeons the player must have completed. Note: "Finished" means the "Finish Dungeon" function was used in the required dungeon.
DungeonsComplete: []
# ClassLevel: 1
Rules:
SpawnMobs: false
SpawnAnimals: false
SpawnMonsters: false
AllowBreakBlocks: false
AllowPlaceBlocks: false
AllowEnderpearl: false
AllowChorusFruit: false
AllowBucket: false
PreventPlantGrowth: true
AllowedCommands:
- party
- p
- dungeon leave
- leave
BannedItems: []
CustomBannedItems: []
```
\ No newline at end of file
Clone repository
General Info
  • Commands and Permissions
  • Plugin Config
Guides
  • Your First Dungeon
  • Importing from DXL
Dungeon Elements
  • Dungeon Config
  • Functions
  • Triggers
  • Conditions
Advanced Info
  • Editing Functions in YML