Links
Tags
Creators
Details
1.3.0
Compatibility
Changes
Elemental Arsenal V1.3.0 Update
[Fixes & Optimizations]
Config System Overhaul: Fixed numerous known issues. All configuration changes can now be read and applied correctly without errors.
Visual Update: Updated with a brand new Mod Logo.
[New Mechanic: Wetness]
Acquisition:
Rain: Accumulates 1 stack every 10 seconds (Max 5 stacks).
Water: Instantly gain 5 stacks.
Potions: Applied when hit by any Splash or Lingering Potions.
Decay Mechanism:
Stacks decay gradually when out of water or rain (simulating clothes drying). Re-exposure to water, rain, or potions will reset the decay timer.
Immunity Rules:
Aquatic mobs, blacklisted entities, and entities in the Nether are immune to this effect.
Entering the Nether will strictly clear any existing Wetness effect.
Attribute Effects (Per Stack):
Frost / Thunder Resistance: -10%
Fire Resistance: +10%
Fire Damage Dealt: -10%
Hunger Exhaustion: +5%
Special Interaction:
Taking Fire damage while Wet reduces that damage by 50% and triggers the Steam Cloud reaction.
[New Reaction: Steam Cloud]
Trigger: Deal Fire damage to a target with the Wetness effect.
Effect: Generates a steam cloud. Entities inside suffer from Blindness, and hostile mobs will lose their current aggro target (resets targeting).
[Configuration]
All values mentioned above are fully configurable in the config file.
属性锻造 V1.3.0更新日志
【修复与优化】
配置系统重构:修复了大量已知错误,现在所有配置文件的修改均可正常读取并生效。
更换全新LOGO
【新增机制:潮湿 (Wetness)】
获取方式:
雨中:每 10 秒叠加 1 层(上限 5 层)。
水中:瞬间获得 5 层。
药水:被投掷型或滞留型药水击中时也会获得潮湿效果。
衰减机制:离开水源或避雨后,效果将逐层衰减(模拟衣物风干),重新接触水源或药水将重置倒计时。
免疫规则:水生生物、黑名单生物及身处下界维度的生物免疫此效果。携带潮湿效果进入下界会被强制清除。
属性影响 (每层):
冰霜/雷霆抗性:-10%
赤焰抗性:+10%
造成的赤焰伤害:-10%
饱食度消耗:+5%
特殊互动:受到赤焰属性攻击时,该次伤害减少 50%,并触发蒸汽云反应。
【新增反应:蒸汽云 (Steam Cloud)】
触发条件:对潮湿状态的生物造成赤焰属性伤害。
效果:生成蒸汽云雾,身处其中的生物将获得失明效果,且敌对生物会丢失当前的仇恨目标(消除索敌)。
【配置】
上述所有数值参数均可在配置文件中自定义。
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:DXBmXnC6:ZZ3pr9FC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DXBmXnC6:ZZ3pr9FC"
}

