Tags
Creators
Details
Licensed MIT
Published 5 years ago
Updated 2 years ago
All versions
0.2.0
Beta
Dynamic Surroundings: Fabric Edition 1.20.4-0.2.03 years ago 1,074
Compatibility
Minecraft: Java Edition
1.20.4
Platform
Fabric
Supported environments
Client-side
Changes
Requirements
- JAVA 17+ (I am using Adoptium https://adoptium.net/)
- Fabric Loader >=0.15.1
- Fabric API >=0.91.2+1.20.4
- 100% client side; no server side deployment needed
What's New
- Cloth-Config is no longer embedded in the jar. Mod will use either Cloth-Config or Yet Another Config Library if installed.
- If both are installed Cloth-Config will be used
- If neither are installed, the mod will still work—you just won't have access to the mod configuration menu and will have to make hand edits to the dsurround.json config file.
- Added Forge biome tags. Enables the broadest out-of-the-box support for cross-loader biome mods.
Changes
- Moved clock overlay display to above the hot bar. Seemed dorky to have it above the cross-hair. Rendering is similar to a tooltip, and the text color is a gradient between midnight (Dark Violet) and noon (Sun Glow) colors.
- Auto-disable footstep brush effect at runtime if Presence Footsteps is installed
- Reworked debug overlay screen for better organization. Added information about entities as well.
Fixes
- Rendering of compass overlay is smoother. I forgot to lerp.
- Null reference exception when player spawns outside of build height
- Sometimes the RandomGenerator algorithms for modern Java are not available (for some unknown reason) and will cause Dynamic Surroundings to crash at startup. If it is not possible to create this generator, logic will fall back to using the Minecraft random generator. Reinstalling the modpack from scratch may help.
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:H7fshfpD:mxyxz61N"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:H7fshfpD:mxyxz61N"
}

