Tags
Creators
Details
2.15.0-RELEASE
Compatibility
Changes
New: diagnostics mode
/vdt diagnose on writes down what the plugin sees and decides, so a problem can be looked at
afterwards instead of only while it happens. One file per day in
plugins/ViewDistanceTweaks/diagnostics, one JSON line per entry, no player names.
- A sample every
interval-seconds(60): MSPT, TPS, tick variance, free heap, players, and per world the distances, loaded chunks, players, the highest client view distance, terrain generation and the density bonus. On Folia also the MSPT of every player's region. - Every distance change with the rule behind it, the settings at start and after every
/vdt reload. extra-sample-above-mspt: an extra sample whenever MSPT goes above this value, at most every 10 seconds, so a short lag spike between two samples is not missed. Off by default./vdt diagnose note <text>adds your own line with a timestamp, for example when players report lag./vdt diagnose statusshows today's file and how much was written.- Switches for samples and changes, a world filter, a daily size limit, old days packed as
.jsonl.gzand deleted afterkeep-days. - Off by default.
/vdt diagnose on|offlasts until the next restart,diagnostics.enabledrecords from startup. Send the folder along with a bug report.
Changed
- Decrease reasons name the rule that caused them.
/vdt history, the console line and the diagnostics file used to saydecrease (mspt=11.9, mode=mixed)even when MSPT had nothing to do with it. They now say what it was, for exampledecrease: client view cap (highest client 12 + 1 headroom)ordecrease: MSPT above 47.0 + chunk budget. - The client view distance cap no longer pulls the simulation distance down. Because view distance may never be lower than simulation distance, one player with a low render distance used to slow down farms and redstone for everyone in that world. The cap now stops at the current simulation distance and only holds back increases above it.
- The highest client view distance is held for three minutes. A player switching dimensions no longer makes a world jump down and back up.
Config update
Existing config files get the new diagnostics block added on the first start (config
version 5), switched off. Nothing else needs to change.
Tested
Folia 1.21.11 with bots rendering 6 and 12 chunks: the cap lowered only the view distance, kept the simulation distance, held the higher value for three minutes after that bot left, and every change carried the right reason. Paper 26.3: config upgrade, all diagnostics options, notes, status, the world filter and the packing of old files. 247 automated tests.
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:X7x1kZUF:oHPrtyIw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:X7x1kZUF:oHPrtyIw"
}

