Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 2 months ago
All versions
2.0.0
Release
TFCGenViewer 2.0.09 months ago 75
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Client and server
Changes
- Update to 1.21.1!
- Complete rework to the underlying functionality; TFCGenViewer now has an API! Expect more on it in the docs at some point
- Several reworks to certain visualizer types
- By default, The Biomes VT now shows a lot more biomes to match TFC's expanded biome palette
- The Inland Height VT has been merged with Biome Altitude, which now shows 7 discrete altitudes from very deep ocean to mountain elevation
- The Rivers and Mountains VT now has a flat land color, shows hot spot ages, and has a 'sensitivity' option for river positions
- The Rocks VT now has two options
- 'At surface': If the preview should be created for the surface rock layer
- 'Elevation': The y-level the preview should be created for if 'at surface' is turned off
- Add the Köppen Climate Classification visualizer type, which colors land according to its Köppen climate classification
- The mod is now properly server optional! Players can join servers without TFCGV without any issues, though naturally they will not be able to use the visualizer features
- The permissions system has received an overhaul allowing for more fine-grained control of visualizer permissions
- For the moment, the rock editor sub-screen is unimplemented
- The seed button now also puts the seed into the seed text box when clicked
Note: Currently the wiki is pretty barren and only has pages on using the new permission system and the json types used to define colors. More will be added as I have the time
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:yp9Ot3YC:XDFDdqTR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yp9Ot3YC:XDFDdqTR"
}

