0.16.6+mc26.2-neoforge
Compatibility
Changes
StreamCraft v0.16.6
Multi-party video is back on shared single-player worlds.
If you open your world to LAN, or host it for friends with a session-hosting mod like Essential, StreamCraft now treats it like a real server: a trial (or your existing license) activates the moment the world becomes shared, and your friends can see your webcam and screen shares on Display Blocks again.
What was broken
Since v0.15.1, single-player worlds ran in a fully local mode: your own camera and screen mirrored into your world for free, but nothing was ever streamed to anyone else — even after you opened the world to LAN or invited friends through Essential. Guests saw blank Display Blocks with no explanation, and there was no way to fix it by subscribing. This worked correctly on v0.14.9 and earlier.
What's new in v0.16.6
- Opening your world to LAN, or a friend joining your hosted world, automatically switches StreamCraft to the full licensed mode — same as a dedicated server, including the free trial for new setups.
- Your game picks up the change live: no rejoin needed. If your camera or screen share was already running when the world became shared, toggle it off and on once to start streaming it to your friends.
- Playing truly solo is unchanged: webcam and screen mirroring in your own world stays free and never touches the network.
Notes
- Works with vanilla Open to LAN and with session-hosting mods such as Essential.
- Voice chat remains free everywhere, as always.
- Dedicated servers are unaffected.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| streamcraft-0.16.6+mc26.2-neoforge-linux-aarch64.jar | Unknown | 20.63 MiB | |
| streamcraft-0.16.6+mc26.2-neoforge-linux.jar | Unknown | 30.65 MiB | |
| streamcraft-0.16.6+mc26.2-neoforge-macos-arm64.jar | Unknown | 25.05 MiB | |
| streamcraft-0.16.6+mc26.2-neoforge-macos-x86_64.jar | Unknown | 27.31 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.
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:UUUunIAe:WCJm3RsR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UUUunIAe:WCJm3RsR"
}

