Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 5 months ago
Updated 4 months ago
All versions
1.4.3
Release
Scorched Guns Neoforged 1.4.35 months ago 1,154
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Fixed
- Fixed Scorched Guns armor not being accepted by vanilla armor enchantments by restoring the Minecraft armor item tags for all mod armor sets, masks and respirators.
- Fixed the standard grenade fuse being much shorter than the other timed throwables.
- Restored suffocation damage inside active Choke Bomb clouds while preserving their existing confusion and fire-extinguishing behavior.
- Restored the existing 3D throwable models for grenade and bomb items in first-person, third-person and dropped-item views while keeping inventory icons flat.
- Restored missing Mob Trap and Enemy Turret placements in Scorched Guns structures by syncing the affected structure templates and jigsaw pools with upstream data.
- Fixed visible grenade-round and shotball projectiles rendering as flat item sprites instead of their 3D projectile models.
- Restored projectile damage falloff support from gun data and re-enabled Hullbreaker shotball falloff/visible cannonball rendering.
- Improved Ramrod-style undead advantage detection so modded undead mobs using vanilla undead healing/harming semantics are recognized.
- Restored gun-data armor penetration handling so firearm
armorPenvalues from Scorched Guns gun JSON affect projectile damage against armored targets again. - Fixed Advanced Composter input checks so items registered as compostable through NeoForge's compostable data map are accepted, including compostable items from other mods.
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:GwtIopV4:cwjbjQGl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GwtIopV4:cwjbjQGl"
}

