All versions
1.1.0
Release
ResizeableSubtitles 1.1.0last month 30
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Forge
Supported environments
Client-side
Changes
1.1.0
Line layout & spacing
- New setting Line layout: Separated (default) or Compact
- Separated steps stacked lines by the scaled line box — fixes overlap at the default 135% scale
- Compact keeps vanilla’s fixed 10px step (lines can overlap above ~110%)
- Line spacing slider: 100%–200% of the scaled line box (ignored in Compact)
- Old 1.0.0 configs without these fields migrate to Separated + 1.0 on load
- Settings preview is now a three-line stack and draws after the menu blur (no smear on 1.20.5+)
Access
- Open-settings key bind now registers on Forge and NeoForge too (was Fabric-only in 1.0.0)
- Fabric: settings button in the mod list via Mod Menu (Architectury bridge). Command + key bind still work without Mod Menu
Fixes
- Fabric jars no longer demand an impossibly new Fabric Loader floor
- Forge 1.19.2 / 1.20.1 mixin boot crash (refmap / MixinConfigs pipeline)
- NeoForge 1.21.11 / 26.2 language-loader version ranges
- Correct pack.mcmeta formats per Minecraft version (translations no longer vanish with a dropped resource pack)
- Unreadable config is moved to
resizeablesubtitles.json.bakinstead of overwritten - Forge: server list no longer treats a server without the mod as incompatible (
displayTest=IGNORE_SERVER_VERSION) - Fabric key-bind category shows a real name instead of a raw translation key
Loaders / versions
- Added: Fabric 1.19.2, Forge 1.21.1, Forge 1.21.11
- Dropped: 26.1 / 26.1.2 (Fabric & NeoForge). 26.2 remains
- Architectury API is now required on Fabric and NeoForge (Forge jars do not use it)
Client-only. Existing scale / opacity / auto-align / offsets and config path are unchanged.
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:ssABRLvT:njSlLsWh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ssABRLvT:njSlLsWh"
}

