Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated 2 months ago
All versions
2.2.0
Release
Smooth Scrolling 2.2.02 years ago 14.2K
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platforms
Fabric
Quilt
Supported environments
Client-side
Changes
- New and much better config file format
- all settings should be automatically updated to this new format without any problems
- new setting for Hotbar Rollover
- this setting will enable/disable the rollover animation of hotbar while smoothly scrolling (when you scroll out of bounds and select an item on the other side of hotbar)
- default: True
- new setting for Entry List Scrolling Speed
- this setting will override the vanilla way of determining how many pixels should the widget scroll by (half of the entry height) to a set value
- default: 30 px
- 0 px: vanilla
- The config file can now be modified with the use of an included config screen, which can be accessed through ModMenu
- changes are only saved when you click on "Save and Exit"
- if the config file is corrupted, you will still get default values without it resetting the config file, but the save and exit button in the screen will overwrite the file even if it is corrupted
- you can still modify the config file while the game is running and you can still reload the config values by reloading resources but when you go into the config screen, it will also reload the config file immediately
- Fixed some compatibility issues
- Flow mod used to mess up creative screen smooth scrolling
- Masks weren't being properly applied with the Raised mod
- Some other stuff that I probably forgot about
- This version of the mod will probably not be backported to older versions of Minecraft
- The 1.21.3 port of this version will be coming as soon as possible but I'm not making any promises
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:CllP7wW0:mKGN9ig2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CllP7wW0:mKGN9ig2"
}

