Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 years ago
All versions
0.5.0-1.19.2
Release
Better Paragliders 0.5.0-1.19.23 years ago 1,517
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Client and server
Required content
Changes
V0.5.0 - The Datapack Update!
- Datapacks should now be fully supported & use my own standalone system removing the need for mixins.
- Support for bows via datapacks.
- Support for shields via datapacks.
- Items can now all be overriden via datapacks to make an entirely custom experience for the user.
- Restructure of a LOT more code. Things should be even cleaner now (hopefully).
- Bows & Shields now longer have finicky stamina systems. They should work just as well as the melee one now.
- A LOT of logic has been reworked to happen server side to support datapacks
- Bows & Crossbows now have working support
- Datapacks are now integrated. Still need to polish up the implementation up a bit, but working pretty well as of now.
- Some minor performance boosts as certain calls won't be made nearly as much after the code rework.
V0.4.0 - The Configuration & Parameter Update!
- Added a server and client config (though the client config is purely a placeholder for now).
- Updated Shield stamina costs
- Added a proper mod version check so now the mod will ensure the proper version of every mod is installed.
- Made the difficult choice to remove Combat Roll support. Makes supporting multiple versions more difficult, and just increases the scope of this mod to more than it truly needs to be.
- Refactored & Reorganized a LOT of code. Things are much nicer now, and updates/ports will be a lot easier in the future.
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:xAsaECDH:RBfP5Y9w"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xAsaECDH:RBfP5Y9w"
}


