Included content
| Name | |
|---|---|
![]() | MidnightLib |
apugli:sprinting now has a new field called requires_input, which defaults to false. This doesn't match the behaviour in previous versions, so set this to true if you wish to have the previous logic.modify_scale power type. Requires Pehkui to function. If Pehkui isn't loaded, any powers with this power type will fail to load.crawling, and prevent_entity_selection power types.requires_input boolean field to sprinting power type (Defaults to false).function field to modify_durability_change power type. Can be floor, round, or ceiling. Defaults to floor.self_target_bientity_action, self_nearby_bientity_action, and target_nearby_bientity_action to damage_nearby_on_hit power type. (All optional).attacker_target_bientity_action, attacker_nearby_bientity_action, and self_nearby_bientity_action to damage_nearby_when_hit power type. (All optional).should_damage_condition to freeze power type.compare_dimensions bi-entity condition type.compare_scale bi-entity condition type. If Pehkui isn't loaded, this condition will return true.crawling, and dimensions entity condition types.scale entity condition type. If Pehkui isn't loaded, this condition will always compare to 1.0.damage_nearby_*_hit power types.damage_nearby_on_hit not running at all.damage_nearby_*_hit not considering for the damage_condition field.hover power type's step_assist field not functioning for correcting upper bounds.allow_anvil_enchant's comparison field not defaulting to >=.modify_enchantment_level not syncing its initial values to clients. #58damage_nearby_when_hit using damage_nearby_on_hit's serializable data.fabric-api mod id. #56sprinting power type.fabric dependency in fabric.mod.json to fabric-api. #56| Name | |
|---|---|
![]() | MidnightLib |
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.
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:1qeWG44Y:S60fuRS4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1qeWG44Y:S60fuRS4"
}