All versions
2.1.3+1.21.1-fabric
Release
Via Romana [Fabric- 1.21.1] 2.1.37 months ago 818
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
Via Romana 2.1.3 Changelog:
Improvements:
- Faster path spline animation in map screen:
- Changed config
spline_animation_speedtospline_animation_timewhich now reflects the time it takes for any network to be fully animated.
- Changed config
- Added map optimizations for chunk image setting & getting.
- Added spatial lookup for map updates to improve performance upon block changes.
- Improved block update check logic to return earlier in most cases improving performance.
- Reduce PathGraph sync packet size by optimizing Node structure
- Added
/viaromana syncto force-sync all players PathGraphs in a given dimension. - Altered
Logging Levelstates fromNONE, DEBUG, VERBOSEtoNONE, ADMIN, DEBUGto clarify intended usage, if you were previously usingVERBOSEit will default toNONE.- Generally improved which logs belong to which logging state.
- Added logging to admin-relevant events such as sign links/unlinks.
- Moved
Logging Levelconfig fromMapScreen toVisualsScreen, which still isn't exactly ideal but more accurate than before.
Fixes:
- Made PathGraph sync more robust to prevent players from being unable to interact with/view paths on login.
- Resolved block update check skipping block breaking in some cases.
- Resolves block tags not generating when using
MidnightLib v1.9.0+
Notes:
- Update to the newest Data Anchor version to resolve a TPS issue with
Enhanced Celestials. - Update to the newest Data Anchor version to resolve a crash related to
dataanchor$onTickBlockEntities. - Going forwards
MidnightLib v1.9.0+will be required.
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:FVToiKwr:rbiw6rDN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FVToiKwr:rbiw6rDN"
}

