Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 3 weeks ago
All versions
3.6.0
Release
Outline N' Stuff - Enchantments 3.6.03 weeks ago 992
Compatibility
Minecraft: Java Edition
26.1.2
Platforms
Fabric
NeoForge
Supported environments
Client-side
Changes
🛠️ v3.6.0.
Multiple fixes, most of them with other mods, on every supported version.
1.21.1, 1.21.11, 26.1.2 and 26.2, each on NeoForge and Fabric.
✨ Added
- A proper page in the mod list.
- Special Compatibility with Silent Gear mod.
- Special Compatibility with Elytra Contrails.
- Special Compatibility with Exposure.
🐛 Fixed
- [Reimagined by Reijvi] Its items were not recognized properly. They are now outlined on their real shape.
- 3D models in third person, Outline N' Stuff mode: the outline traced every edge of the model instead of its outer contour. Only the contour remains.
- [Fabric] The mod could silently fail to load under certain conditions. It now asks for the Fabric Loader it needs, so Fabric tells you what to update.
- [Bray's Better Bow & Arrows] The outline now follows the animated arrows.
- The End, with shaders and Euphoria Patches: in rare cases, the outline disappeared depending on its colour.
- [Silent Gear] Tools and weapons are now outlined as a whole, every part included. Enchanted Silent Gear items also show their glint, which Silent Gear hides by default.
- [Elytra Contrails] Giant outline while gliding, and ghost outlines in first person with shaders. The NeoForged port is covered too.
- With shaders, when holding two enchanted items, the second outline could be missing.
- [Exposure] Holding a photo broke the rendering, and standing in front of a camera duplicated your weapon.
- [1.21.11 // 26.1 // 26.2 // Punchy] With "First-Person Armor Sleeves" on, ring mode cut the outline well before the hand.
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:JjiaUeWd:NiiEYhc3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JjiaUeWd:NiiEYhc3"
}

