Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 years ago
All versions
0.6.0-1.19.2
Release
Better Paragliders 0.6.0-1.19.22 years ago 883
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Client and server
Required content
Changes
V0.6.0 - Major Bug Fixes, Datapack Rework, Depletion Effects Rework, & ParCool Support
- Removed support for additional effects when the player runs out of stamina which was causing bugs where the player couldn't receive those effects when they had stamina.
- The player can no longer attack when out of stamina.
- Added support for ParCool actions (For a potential future update that better supports Paragliders).
- Fixed potential bug causing a crash whenever the player tries to draw a bow with depleted stamina.
- Reworked datapack system. Now each mod will only contain a single json file that uses a json array.
- Added multiple checks to ensure the game has as little random crashes as possible.
- Player can no longer perform a vanilla attack when out of stamina.
- Reworked how depleted stamina works for bows and crossbows. Works more consistently now.
- Massive rework to how depleted stamina effects blocking. No more cooldown effects. Shield simply won't be able to lift now.
- Fixed bug causing stamina regen attributes such as idle regen not applying.
- Fixed bug causing attribute names not work be properly linked to the lang file.
- Fixed minor visual bug causing replenished wheel to remain white for too long before disappearing.
- Fixed issue #26, which was causing incompatibilities with various mods by resolving attributes via item instead of item stack.
- Fixed bug that flipped stamina consumption causing dual wielding weapons.
- Mod now just checks for any attribute modifier attached to the ATTACK_DAMAGE attribute instead of attribute modifiers with certain names. This means full support for mods such as Tetra.
- Fixed issue #32, which was causing ranged and shields to not be affected by the server config settings. Also, reworked how server config settings are applied to all actions to be a bit more logical.
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:Wfk8czDS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xAsaECDH:Wfk8czDS"
}


