Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 2 weeks ago
All versions
3.2
Release
3.22 months ago 86
Compatibility
Minecraft: Java Edition
26.2
Platforms
Fabric
NeoForge
Supported environments
Client-side
Changes
🔥 v3.2.0, MINECRAFT 26.2 IS HERE.
The whole mod runs on 26.2. Nothing trimmed, nothing left behind. 1.21.1 is still supported and still gets fixes.
astoutline-3.2.0+mc1.21.1.jarastoutline-3.2.0+mc26.2.jar
Each jar covers NeoForge and Fabric. Client-side only.
✨ Added
- The final GUI. Side panel with tabs, every option where you expect it.
- Advanced GUI settings. The fine controls, in their own section.
- Enhanced Glint system. Saturation, brightness, hue shift, black floor, scroll speed, pulse. Live, no restart.
🔧 Changed
- Every config description rewritten. What each setting does, and what it costs you.
🐛 Fixed
- Enchantment glint missing with shaders in Outline N' Stuff mode.
- [Cataclysm] every item forced to the ring, not just the ones that need it.
- Inventory Particles runes rendering wrong: wrong rune, or small white squares.
- Runes in IP mode had no colour with shaders.
- Runes in IP mode ignored glow colour matching.
- Runes spawning at one fixed point on some modified items instead of the whole weapon.
- Shaders only: a BEWLR item in one hand and a normal item in the other glitched the BEWLR runes.
- Runes causing a significant FPS drop under certain conditions.
- Holding a BEWLR item costing performance.
🤝 Compatibility
- 1.21.1 and 26.2, NeoForge and Fabric.
- Still supported: Iris, Sodium, Punchy, Hold My Items, Gnetum, Accessories, Apotheosis, GeckoLib, AzureLib, ImmediatelyFast, Inventory Particles.
- Known limitation: Draconic Evolution draws its tools straight to the GPU, outside any path an outline can intercept.
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:3IvtcrQu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JjiaUeWd:3IvtcrQu"
}

