Links
Tags
Creators
Details
1.1.0
Compatibility
Changes
Added direct item interactions when looking at an incense block:
- Potions can add effects without being thrown.
- Flint and Steel and Fire Charges prime incenses.
- Blaze Powder extends stored effects.
- Resin Clumps (or Honeycombs in older versions) hide particles, while Shears reveal them.
- The actionbar shows the available interaction, whether effects will be appended or replaced, and when priming is required.
Added configurable priming:
- Priming can be required Never, Once or Always.
- Priming lasts 60 seconds by default and supports infinite negative durations.
- Lightning Bolts, fireballs and flaming Arrows can also prime incenses.
Added support for multiple stored effects:
- Every effect has its own duration.
- Effects can be appended or replaced.
- Matching effects with the same amplifier combine their remaining durations.
- The actionbar cycles through stored effects, displaying each effect's name, duration and color alongside the remaining priming time.
Expanded effect sources:
- Added Tipped Arrows.
- Replaced separate projectile checks with the generic
#incensed:effect_sourcesentity-type tag. - Tagged players and mobs can transfer their active effects through contact, but none are included by default.
- Item, impact and contact sources can be toggled independently.
Completely rebuilt the configuration interface:
- Added separate General, Feedback and Debug screens.
- Added per-setting and full reset controls.
- Added separate configurable particles and sounds for each interaction.
- Added categorized debug logging and per-player message subscriptions.
Added configurable item-usage tags for durability, stack consumption, Glass Bottles and Buckets.
Added Lanterns as smoke-free incense blocks.
Expanded compatibility from data pack formats 71-110 to 48-112, supporting Minecraft 1.21 and newer.
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:NAQLgRid:FzTJzoUk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NAQLgRid:FzTJzoUk"
}

