Links
Tags
Creators
Details
Licensed MIT
Published 5 days ago
Updated 2 days ago
All versions
1.0.0-beta.13-forge
Beta
Diegesis 1.0.0-beta.13 (Forge)2 days ago 1,560
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Added
- Slot option
idle_highlight: the slot's square shows faintly while the cursor is elsewhere. NodeView.setTooltipItem: a node that draws an item itself shows its tooltip and takes recipe viewers' keys, as a slot does.DiegesisClient.items(buffers): buffers for an item a node painter draws, with depth and its enchantment glint.- Menu stations go over to neighbouring stations: the movement keys and the screen edge reach a furnace beside a crafting table.
- Interface option
carry_count_facing: which way the count of the stack in the hand faces.
Changed
- The square under the cursor on an
uprightslot stands in the item's plane, behind it, no longer flat at its foot. - The count of the stack in the hand is turned to the camera (
"carry_count_facing": "up"keeps the old look).
Fixed
- Enchanted items in a scene show their glint again.
- Stack counts drawn on top are no longer cut by a block standing in front of them.
- A multiblock station's scene shown at rest is drawn once, at its main block, no longer again at each of its other blocks.
- A block model lit as a block takes its light from the world block it stands in, so a multiblock's scene is shaded block by block.
- A multiblock's scene stays until all its blocks are back, and its own blocks are never cleared from the camera's way: no holes as the camera flies in or out.
- Stirring a shallow liquid no longer flattens its waves as if under a lid.
- The game no longer crashes on start with AsyncParticles, and its GPU particles fade in front of a station.
- Claim mods such as Open Parties and Claims and spawn protection keep a station closed to players who may not use the block.
- No sliver of the hand stays in view at a station under an Iris or Oculus shader pack.
Thanks to LeDok for the AsyncParticles, claim and shader pack fixes (#5, #6, #7, #8).
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:pyljrXOa:b6mOc1qU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pyljrXOa:b6mOc1qU"
}

