Links
Tags
Creators
Details
1.0.0-SNAPSHOT
Compatibility
Changes
WarpCore
A lightweight, per-warp configurable teleport (warp) plugin for Paper / Spigot 1.21+.
WarpCore focuses on a clean structure, one file per warp, and full per-warp customization including messages, sounds, broadcasts, and cooldowns.
✨ Features
- 🚀 Simple
/warpcommand system - 📁 One YAML file per warp (no messy
warps.yml) - ⏱️ Per-warp cooldown support
- 🔊 Per-warp teleport sounds (Registry-based, 1.21 compatible)
- 📢 Optional broadcast messages
- 🔐 Permission-based admin controls
- 🎨 Fully configurable messages with placeholders
- ⚡ Lightweight and performance-friendly
📦 Requirements
- Paper / Spigot 1.21+
- Java 21+
🔧 Commands
| Command | Description | Permission |
|---|---|---|
/warp <name> |
Teleport to a warp | warpcore.warp.use |
/warp create <name> |
Create a warp at your location | warpcore.warp.create |
/warp delete <name> |
Delete a warp | warpcore.warp.delete |
🔐 Permissions
| Permission | Description | Default |
|---|---|---|
warpcore.warp.use |
Use warp command | true |
warpcore.warp.create |
Create warps | OP |
warpcore.warp.delete |
Delete warps | OP |
warpcore.warp.admin |
Full warp administration access | OP |
warpcore.cooldown.bypass |
Bypass warp cooldowns | OP |
⚙️ Configuration
📄 config.yml (Messages)
messages:
user-usage: "&cUsage: /warp <name>"
admin-usage: "&cUsage: /warp create <name>\n&cUsage: /warp delete <name>"
no-permission: "&cYou do not have permission to use this command."
only-player: "&cThis command can only be used by players."
warp-not-found: "&cWarp &e{warp}&c does not exist"
warp-create-success: "&aWarp &e{warp}&a has been created successfully."
warp-create-fail: "&cFailed to create warp."
warp-delete-success: "&cWarp &e{warp}&c has been deleted successfully."
📁 Warp Data Files
Each warp is stored as its own YAML file inside the warps/ folder.
Example: plugins/WarpCore/warps/spawn.yml
location:
world: world
x: -260.69999998807907
y: 72.0
z: -134.402189877212
yaw: 76.35025
pitch: 42.300022
teleport-message: "&aTeleported to warp &e{warp}&a."
teleport-sound-enable: true
teleport-sound: "entity.enderman.teleport:1.0:0.9"
broadcast-enable: false
broadcast-message: "&e{player} &7teleported to warp &e{warp}&7."
cooldown: 10
cooldown-message: "&cYou must wait &e{time} &cbefore using this warp again."
🔊 Teleport Sounds
WarpCore uses Registry-based sound keys, fully compatible with Minecraft 1.21+.
Sound Format
sound_key:volume:pitch
Example
teleport-sound: "item.chorus_fruit.teleport:1.2:1.1"
🧠 Placeholders
| Placeholder | Description |
|---|---|
{warp} |
Warp name |
{player} |
Player name |
{time} |
Remaining cooldown time (seconds) |
📜 License
MIT License
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:BTFAwJkB:wgaFAMHL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BTFAwJkB:wgaFAMHL"
}

