Tags
Creators
Details
2.6.0
Compatibility
Changes

π SpawnElytra v2.6.0 - Custom Areas & Flight Timer Update
π― Major Changes
- πΊοΈ In-game area setup - Draw a custom rectangular spawn area or move its center without editing a single coordinate by hand
- β±οΈ Max flight duration - Optional time limit with a boss bar/title countdown, closes the old infinite-flight exploit
- π¬ messages.yml - Every player-facing message is now customizable in its own file
β¨ What's New
New Features
/spawnelytra setup: Stand at two corners, runpos1/pos2/save, done - a live particle preview shows you the box as you set it up, and a gold flash confirms it saved/spawnelytra center [reset]: Set a custom flight-area center independent of the vanilla world spawn- Rectangular spawn areas:
spawnAreaMode: rectangleas an alternative to the radius, with an automatic square fallback sized tospawnRadiusif you don't set up a custom box /spawnelytra visualize [seconds]: Outlines the current area (circle, sphere, or box wireframe) with particlesmaxFlightDuration: Force-land players after N seconds, no fall damage, with a boss bar and last-3-seconds title countdown (sounds and each display element are individually toggleable)- Multiple boosts per flight:
totalBoosts+boostToBoostCooldown, with an actionbar countdown between boosts messages.yml: Boost/activation/flight-timer text, with&color codes and%key%/%count%/%total%/%seconds%placeholders
Enhancements
disableFireworksInSpawnElytrablocks firework-rocket boosting while using the virtual elytra (real elytras unaffected)disableInAdventureoptionally disables flight in Adventure mode; Creative is always excluded now (it has its own native flight)/spawnelytra inforeports the actually active area mode and center, sincearea.ymlcan silently take priority overconfig.ymlconfig.ymlreorganized (Quick Start / Boost Limits / Flight Duration / Advanced Settings) so common options aren't buried under everything else
Bug Fixes
- Permissions did nothing:
spawnelytra.use/.useboostwere declared but never actually checked in code - Reload left stale state:
/spawnelytra reloadnever unregistered the previous listener, causing duplicate event handling and resetting Bedrock-player detection to empty for anyone already connected - Flight could get stuck on: players already granted flight before a reload were never re-tracked, so leaving the spawn area afterward didn't revoke it
- Creative/Spectator flight got disabled: switching modes mid-flight could strip native flight from modes that manage their own, independent of this plugin
- Firework boost bypass: rockets could still boost players using the virtual elytra even with the block option on
- Bedrock chestplate backups now live on the player's own data instead of a separate JSON file
π₯ Installation
Download SpawnElytra-2.6.0.jar and place it in your plugins folder.
π Upgrading
Your existing config.yml keeps working - new options fall back to sensible defaults, and a fresh messages.yml is created automatically on first start.
β οΈ Important Notes
The message key (Java activation text) moved out of config.yml into messages.yml as javaActivation. If you'd customized it, copy your text over - the old key in config.yml is no longer read.
π Why This Update?
- β Set up a custom spawn area entirely in-game, no coordinate math
- β Optional flight-time cap for servers that don't want players gliding forever
- β Every message is now yours to rewrite
- β Drop-in upgrade - your existing config keeps working
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:NAFqBu99:cAGwt7Qk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NAFqBu99:cAGwt7Qk"
}

