All versions
0.2.0
Release
Create ReAutomated: Traces 0.2.05 months ago 232
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Changelog
[0.2.0]
Added
- Trace Finder discoveries are now dimension-aware, so traces at the same coordinates in different dimensions no longer conflict.
- Trace index scan versioning now forces a one-time conservative rescan of older indexed chunks.
Changed
- Trace generation now supports underwater and lava-covered terrain by anchoring traces on the solid bed below the fluid.
- Ice-covered water now behaves like underwater terrain, so traces spawn on the water body's bed instead of on top of sea ice or iceberg ice.
- New traces are indexed at the actual mapped trace block inside the generated template instead of an estimated center/top position.
- Create is now declared as a required dependency because bundled recipes and default zinc trace mappings reference
create:*resources. - Network payload protocol bumped to version
3.
Fixed
- Fixed stale Trace Finder beams and compass targets after changing dimension.
- Fixed valid traces being removed from the index when the saved position did not exactly match the visible trace block.
- Fixed Trace Finder accepting arbitrary client-sent node ids.
- Fixed generated features reporting success even when no trace was actually placed.
- Fixed trace placement rejecting fluid-covered terrain entirely.
- Fixed traces clearing logs while looking for or preparing an anchor.
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:3BTcgJjC:b2pnFcpl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3BTcgJjC:b2pnFcpl"
}

