Tags
Creators
Details
1.1.5
Compatibility
Required content
Changes
- Added proper rendering to the Aura Node entity (Pull Request #3 by Favouriteless
- Gave Aura Nodes conditional transparency based on a condition similar to how aspects are shown on tooltips. I modifed the rendering code to make it transparent by default and only show fully when a condition is met. The Aura Node visibility should be completely configurable by other mods using the API now, with no default condition.
Usage Example for Other Mods
Other mods using your library would need to add their own visibility conditions:
// In another mod's client initialization
AspectsAPI.addAuraNodeVisibilityCondition((player, hasAspects) -> {
// Example: Show nodes when player has a specific item
return player.getMainHandStack().isOf(Items.NETHER_STAR);
});
// Or example: Show nodes when player is in creative mode
AspectsAPI.addAuraNodeVisibilityCondition((player, hasAspects) -> {
return player.isCreative();
});
// Or example: Show nodes when player has a specific effect
AspectsAPI.addAuraNodeVisibilityCondition((player, hasAspects) -> {
return player.hasStatusEffect(StatusEffects.NIGHT_VISION);
});
Default Behavior Now
- By default: Aura nodes are semi-transparent (20% opacity) because no conditions are met
- When conditions are added via API: Nodes become fully visible (100% opacity) when any condition returns true
- Completely pluggable: No built-in logic - entirely driven by API consumers
This makes the library modular and allows each mod that uses it to define its own conditions for when Aura Nodes should be visible.
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| aspectslib-1.1.5-sources.jar | Unknown | 256.12 KiB |
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:zWaybCf1:OwxaPgrR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zWaybCf1:OwxaPgrR"
}

