Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated last year
All versions
1.3.0
Release
v1.3.0-mc.1.12.23 years ago 62.7K
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Changes
Features:
- Captured paintings now appear in the creative tab and in JEI (feature backported from Vanilla 1.19.4).
- New
/jsonpaintings&/paintingscommands, allows users to reload their paintings.json file in-game. - New
PaintingUpdateEventevent, fires whenever a painting entity is updated inEntityPainting::onUpdate. - New tags:
alwaysCapture(optional) - If this is set to true, the painting will always be captured when broken. For each painting, this value defaults to whatever theisCreativetag is set to.mapping(optional) - Set this to any old (removed) painting mantles that should remap to this painting during runtime. Useful if you want to remove a painting without its data being totally lost from existing worlds.rarity(optional) - The rarity of the painting (cosmetic only). This value defaults to "Epic" if theisCreativetag is set to true, otherwise it defaults to "Uncommon". Custom rarities can be supplied as well, to do so: specify a name for the new rarity and the color.
- Painting item tooltips for captured paintings now include the painting's dimensions (i.e. 1x1, 1x2, etc).
- Painting item tooltips now include the mod that added it (while ModNameTooltip is installed).
- The One Probe (TOP) mod support.
Changes:
- ARR license.
- Improved Hywla painting display.
Bug Fixes:
- Fix a possible auto-generated bad reference to a painting's back & side textures (i.e. "textures/textures/-...-.png.png").
- JEI now handles recipes for uncaptured paintings seperately from captured ones.
- Painting item tooltips are now handled better, one side effect to this is that the tooltips now render above the item's mod id if ModNameTooltip is installed.
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:L55Wy0Fz:QBprvpeM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L55Wy0Fz:QBprvpeM"
}

