All versions
1.0.25-neoforge-1.21.1
Release
CC:DirectGPU 1.0.25-neoforge-1.21.13 weeks ago 1,237
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
"Added:
- Create: Pocket Sized support (sable scaling)
- Resolution support like gpu.autoDetectAndCreateDisplay(320, 200), also works with createDisplay and resolution multiplier is now (0.1) - (4)
- Functions:
- clipRect
- clearClip
- loadBlurredImage
- loadBlurredImageBytes
- restoreBackdrop
- clearBackdrop
- loadCoverImageRegion
- loadCoverImageRegionBytes
- get3DStats
- enableMouseEvents
- enableMouseEvents(displayId, true/false): turns mouse events on or off for a display. When off, you can click through it and use scroll etc etc.
- Server config limits:
- maxUpdatesPerSecond
- maxKBpsPerDisplay (0 = unlimited)
Fixed:
- Fixed a bug where autoDetectMonitor("monitor_1") stopped finding monitors behind a wired modem after a recent update. It works again.
- Draw calls and jpg rendering, including a fullscreen jpg with a smaller overlay jpg
- Optimized 3D rendering, including its network packets, so servers can handle it far better (3D on a 3x3 monitor used to overwhelm low-end servers like old laptops)
- Displays rendering with grassier grass messing and distorting the display render and other ingame renders, create contraption controls wont show through displays anymore, including other renders etc
- Clicking displays from any distance, now uses normal block reach and cant click through blocks
- Anti aliasing giving text a black outline
- Many more fixes

Jar is a bit bigger due to the new rendering fixes and network packet optimizations."
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:y2LA8uQE:CFRJ0qJr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y2LA8uQE:CFRJ0qJr"
}

