Tags
Creators
Details
Licensed ARR
Published 10 months ago
Updated 10 months ago
All versions
3.1
Release
Reglia 3.110 months ago 22
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Reglia v3.1 - The GIF Update
Supported Version: Minecraft 1.21.1
This is a massive overhaul from v1.0, introducing a fully integrated GIF ecosystem, a robust Discord bridge, and a completely rewritten rendering engine.
New Features
- In-Game GIF Selector (Press 'G'):
- Browse trending GIFs or search Tenor directly from inside Minecraft.
- One-click to send GIFs to chat.
- Advanced In-Game Rendering:
- GIFs now render natively in the Minecraft chat HUD.
- Smart Layout: GIFs are displayed on their own line with the Sender's name preserved above no more "invisible" senders!
- Refined Discord Bridge:
- Bi-Directional: Chat flows seamlessly between Minecraft and Discord. Clean Links: When you send a GIF in-game, Discord users get a proper Tenor link.
- Minecraft View: When Discord users send a link, Minecraft users see the actual rendered GIF!
Major Improvements & Fixes
- Rendering Engine Rewrite:
- Motion Artifacts Fixed: Implemented Accumulative Frame Compositing to handle optimized GIFs perfect. No more "black holes" or flickering pixels in moving GIFs.
- Color Correction: Fixed an issue where Tenor GIFs appeared blue-tinted. Colors are now accurate.
- Chat Overlap Eliminated: Implemented physical line reservation so GIFs never block subsequent chat messages.
Performance:
- Optimized the tag detection system to have zero impact on FPS when not using GIFs.
- Asynchronous downloading ensures the game never freezes while fetching animations.
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:ybzSyCe7:5QhjbIHu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ybzSyCe7:5QhjbIHu"
}

