Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 months ago
Updated last month
All versions
1.5.5
Release
Trigger Mobs 1.5.54 months ago 662
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Version 1.5.5 (NeoForge / Minecraft 1.21.1)
- Build: NeoForge Gradle picks up local Create:Gunsmithing jars named
create-gunsmithing-*.jaras well ascgs-*.jar/cgs*.jarfromcommon/libs/(artifact rename no longer skips the local jar). - Compatibility: Shipped
minecraft:is_projectiledatapack extension addsntgl:energyalongsidentgl:bullet,ntgl:fire, andntgl:explosive(matches NTGL damage types). - Dependencies: Default Maven fallback versions in
gradle.propertiesupdated to NTGL 1.21.1-3.1.3 and CGS 1.4.5 when no matching jars are present incommon/libs/.
Version 1.5.4 (NeoForge / Minecraft 1.21.1)
- 1.5.4:
neoforge.mods.toml— optional integrations (guardvillagers, cgs) use NeoForgetype = "optional"; neoforge, minecraft, and ntgl usetype = "required".
Version 1.5.3 (NeoForge / Minecraft 1.21.1)
- 1.5.3: Monsters never use gun AI against another monster (
MobGunAttackGoal). - Port to NeoForge with
neoforge.mods.tomland[[mixins]]config. NtglServerPlayHandlerAggroMixin— Skip NTGL’s hostile sound-radius aggro sweep for non-player shooters.MobGunAttackGoal— Target validity (no monster-vs-monster shooting); piglin aggression guard; NTGLGunAttackGoalstripped for monsters/guards holding NTGL weapons.- Config bootstrap no longer reads Forge config getters before the common spec loads (avoids spurious “config not loaded” errors).
Version 1.5.2 (Forge 1.20.1 — Loot Integrations)
- Loot JSON: explicit
minecraft:uniformwhere required; attachment / ammo entry fixes for CGS + Forge parser expectations.
Version 1.5.1 — 1.5.0 (Forge 1.20.1 — Recruits)
- Optional Recruits crossbowman gun AI, finite ammo, recruit CGS replace options — Forge 1.20.1 builds only.
Optional dependencies
Any compatible version
Unavailable version
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:zTVBLVOy:6NoebJHI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zTVBLVOy:6NoebJHI"
}

