Tags
Creators
Details
All versions
1.4.5-1.21.10
Release
fancytoasts v1.4.5 fabric 1.21.108 months ago 2,709
Compatibility
Minecraft: Java Edition
1.21.10
Platform
Fabric
Supported environments
Client-side
Required content
Changes
New features:
- Advancements filtering! Can be changed types of advancements, toasts and even specific advancement or whole categories to enable/disable
- FTBQuests support! Now quests from FTBQuests can be seen on the screen in new fancy way!
- Announcement text -> Quest's announcement
- Title text -> Quest's title
- Description text -> Quest's subtitle (fallback: toast's announcement)
- Texture type
Landspaper - Toast advanced positioning. It supports anchor system with offsets relative to this anchor
- Customizable loops. Now strength and speed of them (sin/cos waves) can be changed
Bug fixes:
- Key bindings don't register sometimes
- Credits' vignette offset
- 1.21.1 and lower: tooltips not being rendered properly under toast with
transparentsetting - 1.21.1 and lower: double click sound when opening a screen with sliders
- EMI compatibility issue
- Badoptimizations compatibility issue
- Too dark credits screen list
Adjustments:
- Total refactor. More robust loadings, easier maintain, and less future compat issues (hopefully)
- Pitch difference for Advancement Toast sounds
- Toasts sound timing tweaked
- Custom textures are now loaded until the last toast using it is shown. Prevents missing textures and memory leaks
- Splashes
- Settings screens aren't closed after saving. It's for easier tweaking of toasts' position and etc.
- Better visual settings UI
- Better translations (in term of keys, and maybe slightly improved English version)
- Toast Control won't disable Fancy Toasts anymore, but they still conflict
Optional dependencies
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:eUziWqPC:D6QZoZKP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eUziWqPC:D6QZoZKP"
}


