Included content
| Name | |
|---|---|
This update revamps nearly every single config option available in Scorchful. Many options that were once values have been converted into multipliers. This allows you to achieve the same effect, while still giving me room to change things behind the scenes without messing up your config settings. All config files will be automatically upgraded and fixed to fit the new schema. Some bugs were also fixed with this update.
Note that as part of this update, the config translations have been removed, as many of them changed too significantly for me to preserve. The other translations are fine, only the config translations have been affected.
heatingMultiplier and coolingMultiplier. These allow you to easily configure all temperature changes of their respective class in one go, without needing to tediously set individual temperature sources.1 -> 6.The client config was removed and split in two: 'Accessibility Settings' and 'Display Settings'. Accessibility settings contains all client-side only options that were added to make Scorchful more accessible to different groups of end users. This is where you will find the options to disable the sound temperature effect, disable effect post-processing features, and to tweak the darkness of the Sun Hat.
The display settings contains the other rendering settings like status bar overlays and drip particles.
Several new options based on floating-point multipliers were introduced where raw values used to be required. Existing values were renamed and normalized based on their original default value. This means that, for example, if you set the old onFireWarmRate option to 36, it would be renamed to burningTemperatureMultiplier and then divided by its original default value of 24 to get a final setting of 36 / 24 = 1.5. Or more simply, if you had "onFireWarmRate": 36, it was converted to burningTemperatureMultiplier: 1.5.
| Name | |
|---|---|
| File | Type | Size | |
|---|---|---|---|
| scorchful-0.16.1+1.21.10-sources.jar | Unknown | 1 MiB |
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.
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:SZQ5qcdn:ulvPdglH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SZQ5qcdn:ulvPdglH"
}