Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 5 months ago
Updated 4 months ago
All versions
1.4.1
Release
Scorched Guns Neoforged 1.4.15 months ago 840
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added
- Added optional Fungal Infection: Spore compatibility: Scorched Guns respirators and ExoSuit gas mask modules can block Spore's mycelium infection effect, and Spore gas masks now count as Scorched Guns gas masks for sulfur gas protection.
Fixed
- Reduced mob fleeing overreaction to automatic gunfire by throttling flee reactions per entity and softening the initial panic knockback.
- Removed forced raid saved-data disk writes from regular level ticks; raid state now marks data dirty and relies on normal autosave, reducing periodic server lag spikes.
- Fixed dedicated-server turret visual rotation on normal blocks by moving turret yaw/pitch visuals to a lightweight server-to-client sync packet with safe shortest-path yaw interpolation.
- Fixed turret visual sync startup and client interpolation so turrets no longer freeze on the first target, spin wildly, or shake while tracking targets in singleplayer and dedicated servers.
- Restored upstream gunner mob weapon-tier pools so progression-based zombie/skeleton-style gunners no longer roll the wider player weapon pool added during content parity work.
- Restored upstream-style gunner and raid mob damage scaling by difficulty, including the configurable mob gun damage multiplier, so AI-held guns no longer deal full player weapon damage.
- Restored upstream-style gunner fire-rate and reload timing controls, including mob fire-rate and burst-delay multipliers, while preserving mob-gun ammo cleanup when weapons drop to players.
- Fixed a server crash when enemy turret projectiles hit players and advancement checks tried to serialize a projectile with an empty pickup item stack.
- Fixed Supply Scamp patrol sorting so modded barrel inventories, including Sophisticated Storage barrels, are recognized through NeoForge item-handler capabilities.
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:TAXtfOvW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GwtIopV4:TAXtfOvW"
}

