2017-05-20 23:09:53 +02:00
|
|
|
###########################################################################################
|
|
|
|
# This is a YML file. Be careful when editing. Check your edits in a YAML checker like #
|
|
|
|
# the one at http://yaml-online-parser.appspot.com #
|
|
|
|
###########################################################################################
|
|
|
|
|
|
|
|
### Credits ###
|
|
|
|
# Tastybento: maintainer
|
|
|
|
# Poslovitch: maintainer
|
|
|
|
#
|
2017-12-22 14:25:22 +01:00
|
|
|
# This translation is adapted to version : [alpha-1]
|
2017-05-20 23:09:53 +02:00
|
|
|
|
2018-04-23 21:16:08 +02:00
|
|
|
banner:
|
|
|
|
- "BLUE"
|
|
|
|
- "STRIPE_DOWNLEFT:WHITE"
|
|
|
|
- "STRIPE_DOWNRIGHT:WHITE"
|
|
|
|
- "STRIPE_CENTER:WHITE"
|
|
|
|
- "STRIPE_MIDDLE:WHITE"
|
|
|
|
- "STRAIGHT_CROSS:RED"
|
|
|
|
- "CROSS:RED"
|
|
|
|
|
2017-05-20 23:09:53 +02:00
|
|
|
not-setup:
|
|
|
|
header: |-
|
|
|
|
More set up is required before the plugin can start...
|
|
|
|
Edit config.yml. Then restart server.
|
|
|
|
distance: "Make sure you set island distance. If upgrading, set it to what it was before."
|
|
|
|
generator: |-
|
|
|
|
The world generator for the island world is not registered.
|
|
|
|
Potential reasons are:
|
|
|
|
1. If you are configuring the island world as the only server world
|
|
|
|
Make sure you have added the world to bukkit.yml
|
|
|
|
2. You reloaded instead of restarting the server. Reboot and try again.
|
|
|
|
generator-multiverse: " 3. Your Multiverse plugin is out of date. Upgrade to the latest version."
|
|
|
|
world-name: |-
|
|
|
|
The world name in config.yml is different to the world name in islands.yml.
|
|
|
|
If this is intentional, we assume you are doing a full reset.
|
|
|
|
If so, delete islands.yml and the previous world.
|
|
|
|
If not, correct the world name in config.yml and restart. This is probably the case if you are upgrading.
|
|
|
|
config-outdated: |-
|
|
|
|
The config.yml file looks outdated.
|
|
|
|
Make sure you updated your configuration after upgrading.
|
|
|
|
If this error is still happening, you probably edited the old config rather than editing the new one.
|
|
|
|
If so, please remove the current config.yml, work on config.new.yml and rename it to config.yml.
|
|
|
|
|
|
|
|
general:
|
|
|
|
success: "Success!"
|
|
|
|
errors:
|
|
|
|
no-permission: "You don't have permission to execute this command."
|