Tags
Creators
Details
0.3.1+1.21.1
Compatibility
Changes
Version 0.3.1
Additional functionalities to Lsky Pro uploader
When using S3/R2/OSS/COS etc. as storage backend at Lsky Pro, it still serves thumbnail image from local storage. Configuration entries were added to allow thumbnail images to be also served from CDN.
localThumbGeneration: If set totrue, generates a thumbnail locally and uploads two images separately, disregarding Lsky Pro's thumbnail response.cdnImageTransform: Specify a URL transform to your S3/R2/OSS/COS/whatever's image scaling endpoint, disregarding Lsky Pro's thumbnail response. Do check out their pricing before enabling this.- Example (Cloudflare): "/cdn-cgi/image/width={thumbWidth}/{path}"
- Available replacement variables:
{path}: the original path component of the URL of the uploaded file inside the bucket.{thumbWidth}: Currently always 256.{quality100}: Currently always 85.{quality1}: Currently always 0.85.
Version 0.3.0
Optional opt-in styled comment display preference
An item called "Comment Eyeglass" has been added. It can be worn on helmet slots or Accessories' "Face" slot if you have the mod installed. (Note that currently the slot integration only fully works in 1.21.1)
This item has no effect by default, but you can configure comments to only show when it is worn.
Associated config item commentVisibilityCriteria and markerVisibilityCriteria has been added. They can be set to tool_toggle, glass_worn, always or never.
Commands
Several client commands has been added to allow accessing comment sending and list screen without in posession of an item.
/wcor/wc send: Opens the sending screen. When opened this way, comments are posted at the player's standing position, skipping the "putting down" phase./wc list: Opens the list screen
Image Global Kill
Server operators can use the command /wcs imageGlobalKill true to globally prevent clients from viewing any image, as a moderation measure.
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:GNAofCJ3:63qjleTu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GNAofCJ3:63qjleTu"
}

