Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
TerraTrees version 2.0.0
This version adds the following:
- The /terratrees spawnstructure command
This command will spawn a Terra structure at the specified location. There are many ways of using it;
/tt spawnstructure structure-terrascript-loader:example world 0 64 0 - This will spawn the structure "example" at x=0 y=64 z=0 in the world "world".
/tt spawnstructure structure-terrascript-loader:example world 0 0 - This will spawn the structure "example" at x=0 z=0 and the current y level as the entity that issued the command in the world "world"
/tt spawnstructure structure-terrascript-loader:example world RabbitTV - This will spawn the structure "example" in world "world" and the coordinates of player "RabbitTV". Also supports UUIDs for both players and entities.
/tt spawnstructure structure-terrascript-loader:example RabbitTV - This will spawn the structure "example" exactly where the player "RabbitTV" is standing. Also supports UUIDs for both players and entities.
/tt spawnstructure structure-terrascript-loader:example - This will spawn the structure "example" exactly where the entity or player that issued the command is.
- The /terratrees liststructures command
This command will list all available structures and also print them to structure_list.txt in the plugins folder.
- The /terratrees reload command
This will reload all configs
- A new configuration file for all the messages. Supports MiniMessage.
Bug fixes:
-
Now compatible with servers running 1.21.10 and higher. This version is not backwards compatible with versions lower than that.
-
Fixed a bug where the 2x2 jungle tree was not getting aligned.
-
Renamed default trees so they work again with overworld 2
-
A lot of internal code improvement.
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:KJXvZ7EY:L4ddKzjf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KJXvZ7EY:L4ddKzjf"
}

