Tags
Creators
Details
2.0.0
Compatibility
Changes
MC 1.21.1 - 2.0.0
TrimsEffects major update is now available!
- This new version changes many features of the mod, and adds many of the most desired features.
- First of all, from now on, all trims will give effects, no matter what material they are combined with (previously only diamond and netherite were available by default). Now, all minerals are valid and resin has also been added, which will give night vision.
- By default, if you wear an armor with a trim, it will give you the level 1 effect, so you can wear up to 4 effects simultaneously (configurable), but if you wear a full armor of the same trim, the effect will be level 2. Again, all this is configurable to your liking!
- Now you can combine effects! The same trim will be able to give several effects at the same time, this can be modified to your liking in the mod settings, which by the way, is much larger and configurable! You can configure almost any feature of TrimsEffects.
- Mobs that have armor with trims will also receive effects by default! Of course, you can also disable it in the settings.
- TrimsEffects is now compatible with many other Minecraft mods and items, just edit the settings and you'll see how the effects will be applied!
- Other small tweaks have also been made, such as changes to the default effects for each trim and other bug fixes.
Being such a big update, there might be some small bugs, please feel free to report them and we will resolve them as soon as possible.
Do you need a server to play with your friends?
For exceptional server hosting services, look no further than BisectHosting. Of course, you can install all the mods or modpacks you want, and their support team is always available to help you.
With the code "Lupin" you will get a 25% discount! Click here!
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:BL7ADJ7w:BhZx10J2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BL7ADJ7w:BhZx10J2"
}


