Tags
Creators
Details
Licensed MIT
Published last month
Updated 5 hours ago
All versions
0.3.0-neoforge+mc1.21.1
Beta
Roxy 0.3.05 hours ago 153
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Required content
Unavailable version
Unavailable version
Unavailable version
Changes
0.3.0 changelog:
Features:
- Added a common warnings screen that notifies users if something about their instance is known to cause issues, such as having environmental fog enabled in voxy's config or an AMD user not having the AMD_DEBUG=nohyperz environment variable active.
Fixes:
- Fix issue #25, a native-voxy fluid state related crash that was most commonly reproduced by Lumisene from Supplementaries.
- Improved rendering of models with tint sources in LODs, issue #28. There are still some limitations that are present in voxy's implementation of this system that cannot be avoided.
- Fixed issue #29 where consistent stale LOD generation when Flywheel or Colorwheel were present in no-shader or shader enviornments, respectively.
- Fixed issue #30 where the game would crash upon using the "/voxy import current" command.
- Fixed issue #31 resolving a crash upon re-entering a world that had blocks in it from a mod that had since been removed.
Known Issues:
- Vivecraft is incompatible with Roxy.
- 1.21.6 rendering changes (such as environmental fog and reworked clouds) are not available in 1.21.1, as such to achieve these you must use alternate mods like Atmospherics or Cirrus to achieve these effects over LoD terrain.
Known incompatibilities
Any version
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:Ap78bKTp:Na9e7ZfU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ap78bKTp:Na9e7ZfU"
}

