Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 5 months ago
Updated 4 months ago
All versions
1.2.5
Release
Scorched Guns Neoforged 1.2.56 months ago 297
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Scorched Guns 1.2.5 - NeoForge 1.21.1
Added
- Restored the Scorched Guns gunner mob system.
- Eligible hostile mobs can now spawn with Scorched Guns weapons.
- Gunner weapon tiers now follow player progression.
- Elite gunner variants can equip stronger gear.
- Added weapon drop chance support for gunner mobs.
- Restored the Blunderer raid reinforcement hook.
- Restored data-driven Vent Collector settings.
- Added sulfur and geothermal vent output data.
- Added weighted vent outputs, including rare blaze powder from sulfur vents.
- Restored Bat Guano as a fertilizer/placeable layer item.
- Restored Guano Candles with lighting, extinguishing, sulfur ambience, and bat attraction behavior.
- Restored Phosphor Dust fertilizer/layer behavior.
- Added Phosphor Layer block assets, loot, and localization.
- Restored Vicious Acid, including:
- acid bucket
- fluid block
- acid cauldron
- acid bubble particles
- crafting recipe
- water/lava/fire reactions
- Restored Mine Unit as a grenade-loaded proximity trap.
- Restored Shock Coil as an energy-powered defensive block.
- Restored Metal Detector functionality.
- Added Turret Platform item required by the Shock Coil recipe.
Fixed
- Fixed ADS mouse sensitivity not being reduced while aiming, especially with high-zoom scopes.
- Fixed gunner mob tier progression so higher-tier weapons are recognized correctly.
- Fixed progression-based gunner mobs choosing empty weapon tiers.
- Fixed ExoSuit upgrade visuals not appearing on the armor model in some cases.
- Fixed Bat Guano and Phosphor layers not dropping their source items when broken.
- Fixed Vent Collector weak filter data so wool works as the intended low-tier filter.
- Fixed Mine Unit behavior so non-living helper entities no longer trigger armed mines accidentally.
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:3A2m0X9w"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GwtIopV4:3A2m0X9w"
}

