Guest User

Untitled

a guest
Sep 18th, 2025
21
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.58 KB | Gaming | 0 0
  1. ####################################################################################################
  2. # #
  3. # █▀▄▀█ █░█ █░░ ▀█▀ █ █░█ █▀▀ █▀█ █▀ █▀▀   █▀▀ █▀█ █▀█ █▀▀ #
  4. # █░▀░█ █▄█ █▄▄ ░█░ █ ▀▄▀ ██▄ █▀▄ ▄█ ██▄   █▄▄ █▄█ █▀▄ ██▄ #
  5. # #
  6. # #
  7. # WIKI: https://github.com/Multiverse/Multiverse-Core/wiki #
  8. # DISCORD: https://discord.gg/NZtfKky #
  9. # BUG REPORTS: https://github.com/Multiverse/Multiverse-Core/issues #
  10. # #
  11. # #
  12. # Each option in this file is documented and explained here: #
  13. # ==> https://github.com/Multiverse/Multiverse-Core/wiki/config.yml #
  14. # #
  15. # #
  16. # New options are added to this file automatically. If you manually made changes #
  17. # to this file while your server is running, please run `/mv reload` command. #
  18. # #
  19. ####################################################################################################
  20.  
  21.  
  22. world:
  23. # When enabled, Multiverse will automatically import default worlds defined in the server.properties
  24. # `level-name` property when the Multiverse is enabled or reloaded. This will include the nether and
  25. # end if the server created them.
  26. auto-import-default-worlds: true
  27.  
  28. # When enabled, Multiverse will import all other worlds created by other plugins when Multiverse starts
  29. # or when Multiverse is reloaded.
  30. auto-import-3rd-party-worlds: true
  31.  
  32. # This setting will prevent players from entering worlds they don't have access to.
  33. # If this is set to false, players will be able to enter any world they want.
  34. # If this is set to true, players will only be able to enter worlds they have
  35. # the `mv.access.<worldname>` permission.
  36. enforce-access: false
  37.  
  38. # Sets whether Multiverse will should enforce gamemode on world change.
  39. # If enabled, players will be forced into the gamemode of the world they are entering, unless they have
  40. # the `mv.bypass.gamemode.<worldname>` permission.
  41. enforce-gamemode: true
  42.  
  43. # Sets whether Multiverse will should globally enforce flight ability on worlds.
  44. # Disable this if you want another plugin to handle player's flight ability.
  45. # Disabling this will make the world property `allow-flight` have no effect.
  46. enforce-flight: true
  47.  
  48. # Sets whether Multiverse will purge entities on world load based world's entity spawn config.
  49. auto-purge-entities: false
  50.  
  51. # Format for world names for multiverse to automatically detect a world group consist of overworld, nether and end.
  52. # This is used default-respawn-in-overworld and potentially other features.
  53. world-name-format:
  54. nether: '%overworld%_nether'
  55. end: '%overworld%_the_end'
  56.  
  57.  
  58. teleport:
  59. # Sets whether Multiverse will use more fine-grained teleport permissions.
  60. # ----
  61. # New finer teleport permissions for /mvtp and /mvspawn commands:
  62. # - For specific teleport types: `multiverse.teleport.<self|other>.<type>.<target>`
  63. # - For specific world spawn: `multiverse.core.spawn.<self|other>.<worldname>`
  64. # For example, if `multiverse.teleport.self.w.world2` is set, Multiverse will only allow the player to teleport to the world2.
  65. # ----
  66. # Legacy permissions will be used if this is set to false:
  67. # - For teleport destinations: `multiverse.teleport.<self|other>.<type>`
  68. # - For spawn: `multiverse.core.spawn.<self|other>`
  69. use-finer-teleport-permissions: true
  70.  
  71. # Configures how passengers and vehicles are handled when an entity is teleported.
  72. # default: Server will handle passengers and vehicles, this usually means entities will not be teleported to a different world if they have passengers.
  73. # dismount_passengers: Passengers will be removed from the parent entity before the teleport.
  74. # dismount_vehicle: Vehicle will be removed and from the parent entity before the teleport.
  75. # dismount_all: All passengers and vehicles will be removed from the parent entity before the teleport.
  76. # retain_passengers: Passengers will teleport together with the parent entity.
  77. # retain_vehicle: Vehicles will teleport together with the parent entity.
  78. # retain_all: All passengers and vehicles will teleport together with the parent entity.
  79. passenger-mode: default
  80.  
  81. # Sets the maximum number of players allowed to be teleported at once with `/mv teleport` command
  82. concurrent-teleport-limit: 50
  83.  
  84. # If this is set to true, Multiverse will enforce access permissions for all teleportation,
  85. # including teleportation from other plugins. You should not disable this unless you are facing
  86. # conflict with another plugin handling teleportation.
  87. teleport-intercept: true
  88.  
  89. # Sets the horizontal (x and z-axis) search radius for finding a safe location to teleport to.
  90. # Increasing this value will widen the search area at the cost of performance.
  91. # To disable, set to 0.
  92. safe-location-horizontal-search-radius: 3
  93.  
  94. # Sets the vertical (y-axis) search radius for finding a safe location to teleport to.
  95. # Increasing this value will widen the search area at the cost of performance.
  96. # To disable, set to 0.
  97. safe-location-vertical-search-radius: 3
  98.  
  99.  
  100. spawn:
  101. # Sets whether Multiverse will override the location where the player spawns when they join the server
  102. # for the first time. For fixed spawn location on every login, see the `join-destination` option below.
  103. # If disabled, it will default to server.properties settings.
  104. first-spawn-override: false
  105.  
  106. # Sets the world that Multiverse will use as the location for players that join the server for the first time.
  107. # This only applies if first-spawn-override is set to true.
  108. first-spawn-location: ''
  109.  
  110. # Enables setting of a fixed location for players to spawn in when they join the server every time.
  111. # See `join-destination` option below as well.
  112. enable-join-destination: false
  113.  
  114. # Sets the destination that Multiverse will use to spawn players on every login.
  115. # Set the above enable-join-destination to false to disable
  116. join-destination: ''
  117.  
  118. # This only applies if the `respawn-world` property is not set for the world that the player died in,
  119. # and the player does not have bed or anchor set.
  120. # ----
  121. # When this option is enabled, players will respawn in the overworld when dying in nether or end, mimicking the vanilla behavior.
  122. # The automatic selection of overworld is determined by the `world-name-format` config section above.
  123. # This option takes precedence over the `default-respawn-within-same-world` option.
  124. # ----
  125. # Set this to false if you want another plugin to handle respawning or do not want this vanilla behavior.
  126. default-respawn-in-overworld: true
  127.  
  128. # This only applies if the `respawn-world` property is not set for the world that the player died in,
  129. # and the player does not have bed or anchor set.
  130. # ----
  131. # When this option is enabled, players will respawn in the same world's that they died in.
  132. # If the /spawnpoint is already within that world and `enforce-respawn-at-world-spawn` is disabled,
  133. # Multiverse will use that spawn location, else it will use the world's spawn where the player died in.
  134. # ----
  135. # You can set `respawn-world` property with the command: `/mv modify <worldname> set respawn-world <worldname>`
  136. # You can reset `respawn-world` property with the command: `/mv modify <worldname> reset respawn-world`
  137. # ----
  138. # Set this to false if you want another plugin to handle respawning.
  139. default-respawn-within-same-world: true
  140.  
  141. # When this option is enabled, players will always respawn at the world's spawn location of calculated respawn world,
  142. # unless bed or anchor is set and `bed-respawn` or `anchor-spawn` is enabled respectively.
  143. # ----
  144. # Set this to false if you want to use a custom spawn location such as /spawnpoint instead of the world's spawn location.
  145. enforce-respawn-at-world-spawn: true
  146.  
  147.  
  148. portal:
  149. # This config option defines whether or not Multiverse should interfere with's Bukkit's default portal search radius.
  150. # Setting it to false would mean you want to simply let Bukkit decides the search radius itself.
  151. use-custom-portal-search: false
  152.  
  153. # This config option defines the search radius Multiverse should use when searching for a portal.
  154. # This only applies if use-custom-portal-search is set to true.
  155. custom-portal-search-radius: 128
  156.  
  157.  
  158. messaging:
  159. # This config option defines whether or not Multiverse should prefix the chat with the world name.
  160. # Ensure this is false if you want another plugin to handle chat formatting.
  161. enable-chat-prefix: false
  162.  
  163. # This config option defines the format Multiverse should use when prefixing the chat with the world name.
  164. # This only applies if enable-chat-prefix is set to true.
  165. chat-prefix-format: '[%world%]%chat%'
  166.  
  167. # This config option defines whether or not Multiverse should register the PlaceholderAPI hook.
  168. # This only applies if PlaceholderAPI is installed.
  169. register-papi-hook: true
  170.  
  171. # This config option defines the default language Multiverse should use.
  172. default-locale: en
  173.  
  174. # This config option defines if Multiverse should use the player's language based on their client's language.
  175. # If the player's language does not have a translation, it will use the default language set above instead.
  176. per-player-locale: true
  177.  
  178.  
  179. command:
  180. # If this is set to true, Multiverse will resolve world based on their alias names for commands and destinations.
  181. # Normal world names will still be accepted.
  182. # In the event you have multiple worlds with the same alias name, the first world found will be used.
  183. resolve-alias-name: true
  184.  
  185. # This config option defines whether `/mv confirm` is needed before running a DANGEROUS action.
  186. # enable: `/mv confirm` is required.
  187. # player_only: `/mv confirm` only required when running command as a player.
  188. # disable_command_blocks: `/mv confirm` not required for command blocks.
  189. # disable_console: `/mv confirm` not required for the console.
  190. # disable: `/mv confirm` is not required.
  191. confirm-mode: enable
  192.  
  193. # If this is set to true, `/mv confirm` will include a 3 digit random number that must be entered to confirm the command.
  194. # For example: `/mv confirm 726`
  195. use-confirm-otp: true
  196.  
  197. # The amount of time in seconds before `/mv confirm` times out
  198. confirm-timeout: 30
  199.  
  200. # If this is set to true, legacy aliases will be shown in tab completion.
  201. # These are old mv4 aliases such as `/mvclone` in addition to `/mv clone` which crowds the tab completion.
  202. # !!!NOTE: This will only apply after a server restart!
  203. show-legacy-aliases: false
  204.  
  205.  
  206. event-priority:
  207. # The follow configuration changes the bukkit's EventPriority for certain events.
  208. # Only ever change this if you need multiverse's events outcomes to override another plugin, or if
  209. # you want another plugin's outcome to override multiverse's.
  210. # ----
  211. # !!!NOTE: This will only apply after a server restart!
  212.  
  213. # This config option defines the priority for the PlayerPortalEvent.
  214. player-portal: high
  215.  
  216. # This config option defines the priority for the PlayerRespawnEvent.
  217. player-respawn: low
  218.  
  219. # This config option defines the priority for the PlayerSpawnLocationEvent.
  220. player-spawn-location: normal
  221.  
  222. # This config option defines the priority for the PlayerTeleportEvent.
  223. player-teleport: highest
  224.  
  225.  
  226. misc:
  227. # Change this if you use a custom path for the bukkit.yml file with `--bukkit-settings` startup flag.
  228. # Note: this config option needs a server restart to take effect.
  229. bukkit-yml-path: bukkit.yml
  230.  
  231. # This is our debug flag to help identify issues with Multiverse.
  232. # If you are having issues with Multiverse, please set this to 3 and then post your log to pastebin.com
  233. # Otherwise, there's no need to touch this. If not instructed by a wiki page or developer.
  234. # 0 = Off, No debug messages
  235. # 1 = fine
  236. # 2 = finer
  237. # 3 = finest
  238. global-debug: 0
  239.  
  240. # Sets whether console will log every permission check done by all multiverse plugins.
  241. # This will only work if the above 'global-debug' is set to 1 or more.
  242. debug-permissions: false
  243.  
  244. # If true, the startup console messages will no longer show.
  245. silent-start: false
  246.  
  247. # If you don't want to donate, you can set this to false and Multiverse will stop nagging you.
  248. show-donation-message: true
  249.  
  250.  
  251. # This just signifies the version number so we can see what version of config you have.
  252. # NEVER TOUCH THIS VALUE
  253. version: 5.2
  254.  
Tags: minecraft
Advertisement
Add Comment
Please, Sign In to add comment