Tags
Creators
Details
0.3.0+1.18
Compatibility
Changes
Changes
The mod has been largely rewritten, basically nothing remained untouched. Most, if not all, major issues and shortcomings of older versions have been fixed and improved - from UI being unclear over Area Renders being janky to the inability to export motion pictures. A small overview of the major changes is as follows
- Area Renders now include entities, block entities and particles. This means blocks like chests now render without needing additional mods like EBE. They also support Fabric Rendering API models when running with Indigo - Indium is currently not supported
- The ability to take snapshots of the viewport has been removed - everything is now rendered through the dedicated pipeline
- The contents of the viewport can now be moved and manipulated with your mouse - try dragging with your different mouse buttons
- Tags can now be exported as batches or atlases
- The Shift+F12, Ctrl+F12 and Alt+F12 shortcuts have all been merged into Ctrl+F12 which now opens a dedicated screen that lets you choose how the render the items of the inventory you're in
- The tooltips of items can now be rendered individually, they are exported with their transparency preserved
- You can now export the render to your clipboard instead of a file, useful for pasting into an image editor for example
Fixes
- Images exported with the dedicated pipeline now always match up perfectly with what the viewport shows
- Item Atlases now render reliably and correctly aligned in all sitations
- Lighting now more closely matches the standard vanilla settings, and the angle can be adjusted for each render individually
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:M0aimenU:CCfN44Ti"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M0aimenU:CCfN44Ti"
}

