Tags
Creators
Details
1.7
Compatibility
Required content
Changes
AnimatedFrames โ v1.7
New options for sharing files from the server and improvements to memory management and connectivity.
New Features
- Files from the server:
/medias shownow sends content to players for playback, without requiring them to copy it to their computers beforehand. This brings back a feature that was already available in AnimatedFrames 1.3.1. - Local playback: new
/medias showlocalcommand to display files the player already has saved, preserving the previous behavior of/medias show. - Server file listing:
/medias listlets you view the files available on the server. - Names with spaces: commands accept filenames in quotes, such as
"welcome video.mp4". Autocomplete adds the quotes automatically.
Improvements
- Optimized file transfers with background reading.
- Separate cache for content received from the server.
- File integrity checks before playback.
- Better memory management for images and GIFs, freeing resources that are no longer in use.
Fixes
- Fixed playback instances accumulating when switching videos, which could cause unexpected game crashes.
- Fixed an issue that prevented commands from running through command blocks and datapack functions to automate multimedia content. Thanks to melmi_melmi for reporting it on Discord.
Key Commands
| Command | Function |
|---|---|
/medias show <player|@a> <file> [time] [position] [scale] [volume] |
Sends and plays a file from the server. |
/medias showlocal <player|@a> <file> [time] [position] [scale] [volume] |
Plays a local file stored on the player's computer. |
/medias list |
Lists the files on the server. |
/medias stop <player|@a> |
Stops playback. |
When updating from 1.6.2: if your commands used files stored on each player's PC, replace
/medias showwith/medias showlocalto preserve that behavior.
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:mAbDCyw6:6xXqbUQA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mAbDCyw6:6xXqbUQA"
}


