Tags
Creators
Details
1.14.0
Compatibility
Changes

TvStudio Fabric: v1.14.0 For Minecraft 1.20
It is time for the release of the next major update; version 1.14. With this update there is more functionality added to the mod. (Please note that the camera's will not be operating in this or any update in the foreseeable future.)
Also a lot of time has been spent on improving old models that were poorly created years ago and never looked at again.
If you come across any bugs, please report them on the bug-tracker.

CHANGES IN 1.14.0
Studio Lightnow activates when clicked (No redstone required)Studio barconnects to itself horizontally- New vertical bar added called
Studio Pillar - New
blue screen wallmodel - New
green screen wallmodel Blue screen wallnow uses the unlimited colouring systemGreen screen wallnow uses the unlimited colouring system- Improved
Director ChairModel - Improved
Tv CameraModel - Improved
Tv StandModel - Improved
Studio LightModel - Improved
SetwallModels- all models are now children of one parent model, this reduces complexity of the mod files.
- Updated Collisionshape of
Setwalls- to prevent walking through them.
- Updated Voxelshape of
Director Chair - Updated Voxelshape of
Tv Camera - Updated Voxelshape of
Tv Stand - Updated model of
Tv Camera On Standto reflect Tv Camera and Tv Stand changes - Updated Voxelshape of
Tv Camera On Stand - Removed colouring function from
headsetitem until further notice
New studio bar System
This new system makes it possible for the studio bar to connect to itself. This is done to support creativity when building with the studio bar, because you are no longer limited to straight lines.

FIXED BUGS IN 1.14
[TS-18] - Tv Camera Voxelshape broken.

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:ivGWJLOr:watQ25g9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ivGWJLOr:watQ25g9"
}

