2.4Kdownloads
4followers
FlyCraft has been archived. FlyCraft will not receive any further updates unless the author decides to unarchive the project.
Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 5 months ago
All versions
1.4.7
Release
FlyCraft 1.4.75 months ago 730
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
[1.4.7] - 2026-03-14
Added
- Multi-Language Support: Complete overhaul of the message system.
- Messages are now stored in a dedicated
lang/folder (default:en_us.yml). - Support for custom language files that are preserved during plugin updates.
- Smart auto-update logic: only official language files receive automatic key additions.
- Messages are now stored in a dedicated
- Next-Gen Configuration & Migration Engine: Complete re-engineering of the config system to support automated, comment-preserving updates. It now intelligently detects and preserves all custom user data (groups, entries, values) during migrations and automatically creates
.oldbackups for safety.
Fixed
- Group Cooldown Logic: Fixed group-specific cooldowns being ignored during automatic flight expiration.
- Manual Toggle Handling: Added tracking for manual flight stops (double-jump) to correctly trigger cooldowns and Discord logs.
- Discord Placeholder Sync: Fixed
%duration%in Discord embeds to accurately reflect group-specific limits. - Config Cleanup: Automated removal of deprecated
messagesandnotification-messagesblocks fromconfig.ymlafter migration. - Resilient Loading: Implemented better type-handling to prevent crashes when invalid data types (like numbers in string fields) are encountered in YAML files.
Optional dependencies
Any compatible version
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:CWMrVT99:rlVj1azG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CWMrVT99:rlVj1azG"
}

