Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated last month
All versions
1.0.37-forge-mc1.14
Release
Tesseract 1.0.372 years ago 33
Compatibility
Minecraft: Java Edition
1.14.x
Platform
Forge
Supported environments
Client and server
Required content
Changes
Tesseract 1.0.37
- Added Turkish translations (thanks to RuyaSavascisi!)
Tesseract 1.0.36
- Fixed data for last placed tesseract sometimes getting overwritten when placing a new tesseract after loading a save
- Added Simplified Chinese translations (thanks to YCJ-GuLi!)
- Updated Russian translations (thanks to Vladislove99!)
Tesseract 1.0.35a
- Fixed tesseract resource transferring with neighboring blocks sometimes breaking
Tesseract 1.0.35
- Fixed player skins inside the tesseract screen not rendering sometimes
Tesseract 1.0.34
- Added Ukrainian translations (thanks to SKZGx!)
- Fixed tesseracts getting stuck not transferring
- Fixed error message when loading a world without previous tesseract data
Tesseract 1.0.33
- Fixed rare crash when invalid tesseract references are removed
Tesseract 1.0.32
- Fixed rare stack overflow error
Tesseract 1.0.31
- Fixed tesseract save data loading
Tesseract 1.0.30a
- Fixed crash on startup
Tesseract 1.0.30
- Significant performance improvements
- Added confirmation screen when removing channels
- Tesseract data will now be saved more frequently
- Fixed player heads not rendering correct skins
- Fixed being able to delete other players' channels
Tesseract 1.0.29
- Added integration with Jade and The One Probe
- Updated Russian translations (thanks to Big Energy!)
Tesseract 1.0.28
- Updated to core library 1.1
- Removed the WIP info button in the tesseract menu
- Added the tesseract to the creative menu decorations tab
- Added text coloring for transfer and redstone settings
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:OUhp5O2m:oPmFz2eO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OUhp5O2m:oPmFz2eO"
}




