Tags
Creators
Details
0.1.0-beta.4+1.21.1
Compatibility
Changes
Features
- You can now right click on radios and cassette decks while holding a cassette tape to insert it directly like you can with jukeboxes.
- The walkie talkie recipe has been modified and no longer requires brass if Create is installed.
- Create display links now receive metadata from radio and speaker blocks as sources.
- Radios will send the audio title and duration for the currently playing cassette tape.
- Speakers will send the name(s) of currently active audio input sources, one on each line (e.g. the usernames of players speaking into walkie talkies received by the speaker).
- Create packagers will now interact with radio blocks like they do with jukeboxes.
- Create deployers and mechanical arms can now insert cassette tapes into radios and cassette decks.
- Hoppers beneath radio blocks will now extract cassette tapes and bags even if they are playing. If you only want the hopper to extract the tape when it is finished playing, use a comparator to read the radio's output signal, and use it to lock the hopper.
- Parrots and mechanical arms will now dance to radios playing audio like they do for jukeboxes.
Fixes
- Radios no longer emit a constant redstone signal as a source instead of a peripheral. #38.
- Cassette tapes without a stored volume override will no longer reset the radio's volume to default. Instead, they will maintain the current volume. #46
A special thank you to arcaneocto for their suggestions regarding improvements to Create integration; those aspects of this update wouldn't have happened without their input.
And as always, please continue reporting any problems you experience to me on Github or on Discord!
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:iMAVG2nH:F0kN20Pn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iMAVG2nH:F0kN20Pn"
}





