All versions
0.3.14.2
Release
Timeless and Classics Guns 0.3.14.22 years ago 385.5K
Compatibility
Minecraft: Java Edition
1.16.5
Platform
Forge
Supported environments
Client and server
Changes
0.3.14.2 RELEASE (1.16.5):
NEW
- Added four ammo plugins for independent parameter control of each weapon;
- Added two config control parameters for locking the guns' level system;
- Added the config control parameter for adjusting duck spead reduction.
- Added config control parameter to control whether bullets are unlimited in survival and creative mode;
- A new synthesis method of four ammo plugins;
- Added M134 machine gun;
- Added the config control parameter for controlling the sound effect of the rotating barrel;
- A new overheating mechanism and four control data parameters; ** Whether it is overheating, tick required for overheating, tick punished for overheating, and recovery speed for each tick **
- Added the mechanism and corresponding data parameters of the direct using the ammo in bag;
FIX
- Fix bolt issue when rpm is set higher than 1200; ** But in 1.16.5, whatever you set the rpm, if it is greater than 1200, it'll only performance as 1200 rpm **
SET
- The base penetration of some weapons has been adjusted; ** FAL(2), G3(2), M60(2), M82(3ā4), SCAR-H(2), SPR15(2ā1) **
- Incendiary will no longer be extinguished by water, and custom content will be added (but the burning animation will be changed);
- Adjusted some GUI Settings (in TaC HUD); ** Now you can adjust the overall position of the GUI or the individual position of the weapon icon **
- Some config options in tac-common.toml are moved to serverconfig.
- The guns' level system has been preliminarily reset; ** The current default will lock the original holder, and others will not be able to enjoy the bonus from the guns' level **
- Change the 16-color skin to disordered synthesis;
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:hudztH4j:HdrWwrST"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hudztH4j:HdrWwrST"
}

