Tags
Creators
Details
1.0
Compatibility
Changes
π¦ DuckyZones v1.0 β First Public Release π
The first official release of DuckyZones β a flexible, lightweight region management system for Minecraft servers!
β¨ Features
- πΊοΈ Define custom zones using two corners
- π Multi-world support
- β Block specific items and potion effects inside zones
- β Require specific items or effects to enter a zone
- πͺ Optional Elytra disabling β automatically removes Elytra when entering the zone
- β€οΈ Health and experience level restrictions per zone
- π§ͺ Automatically apply potion effects inside zones
- π¬ Custom deny messages when entry conditions aren't met
- π In-game config reloading with
/duckyzones reload
π οΈ Command
/duckyzones reload
Reloads the plugin configuration without restarting the server.
π Permissions
duckyzones.reload - Permission to use /duckyzones reload
duckyzones.update - Permission to see Update info in-game
duckyzones.zone.<zone_name> - Permission to enter specific zone
duckyzones.zone.<zone_name>.bypass - Permission to bypass all restrictions to enter specific zone
duckyzones.zones.bypass - Permission to bypass all restrictions to enter any zone
π§Ύ Configuration
Zones are defined in config.yml like this:
# List of Items (1.21.5) : https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Material.html
# List of Effects (1.21.5) : https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/potion/PotionEffectType.html
zones:
spawn: # Zone name
world: world # World where zone is
corner1: world,100,64,100 # First Zone Corner
corner2: world,110,70,110 # Second Zone Corner
elytra-disabled: false # Should be elytra disabled in that zone? This will remove the elytra from the player
elytra-disabled-message: "Elytra is disabled in this zone!"
blocked-items: # Player with these items in inventory cannot enter the zone
- TNT
- ENDER_PEARL
blocked-effects: # Player with these effects cannot enter the zone
- SPEED
- INVISIBILITY
required-items: # Only Player with these items in inventory can enter the zone
- DIAMOND
- TOTEM_OF_UNDYING
required-effects: # Only Player with these effects can enter the zone
- NIGHT_VISION
zone-effects: # Effects that will be applied after entering the zone, after leaving it they will disappear separator; means the power of the effect, e.g. SPEED;1 = Speed 2 in the game
- SPEED;1
- NIGHT_VISION;0
min-health: 5.0 # Players who do not have this number of hearts cannot enter
max-health: 20.0 # Players who have this number of hearts or more cannot enter
min-level: 5 # Players who do not have this amount of exp level cannot enter
max-level: 100 # Players who have this amount of exp level or more cannot enter
deny-message: "&cYou can't enter this area!" # Players who are unable to enter the zone will receive this message in chat when trying to enter
zone-teleport-back-command: "spawn %player%" # The command that will be executed when the player enters the zone e.g. through teleportation, to call the player's nickname, just type %player%
entry-deny-title: "&cEntrance prohibited &4β" # Title that will appear on the screen when a player tries to enter the zone without meeting the requirements
entry-deny-subtitle: "%reason%" # SubTitle that will appear on the screen when a player tries to enter the zone without meeting the requirements
entry-deny-actionbar: "&eGet away from the zone!" # ActionBar that will appear on the screen when a player tries to enter the zone without meeting the requirements
entry-deny-bossbar: "&4Entrance to the zone blocked!" # BossBar that will appear on the screen when a player tries to enter the zone without meeting the requirements
entry-deny-sound: ENTITY.VILLAGER.NO # Sound that will play on the screen when a player tries to enter the zone without meeting the requirements
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:6kd92Ddn:UddodfAc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6kd92Ddn:UddodfAc"
}

