Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 years ago
Updated 5 months ago
All versions
0.7.0-1.20.1
Alpha
[1.20.1] Immersive Backrooms 0.7.03 years ago 4,962
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
- incremented version number
- updated to Minecraft 1.20.1
- added pipe block loot table
- added iron button
- works the same as a stone button
- crafted with an iron ingot in a stonecutter
- added elevator button
- drops iron button when broken
- also removes associated portal entities when broken
- works similarly to portal placer block, with extra features:
- portal facing direction specified manually instead of using block facing property
- only works to specify vertical direction
- otherwise uses block facing property like portal placer
- can specify portal origin offset from button position
- portal placed when testing by shift right-clicking instead of just right-clicking
- animates portal when button pressed with simple 1D translation animation
- portal facing direction specified manually instead of using block facing property
- basically, this is designed to be used as a 1-way interdimensional elevator
- drops iron button when broken
- added elevator door block
- extends vanilla door block class
- custom model and block entity renderer
- renders smooth door open/close animation
- double door behavior
- opening/closing one side of a double door opens/closes both sides
- added level 4 dimension and portal
- makes use of new NoiseThresholdPlacementModifier to place walls where there are no rooms
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| backroomsmod-0.7.0-1.20.1-sources.jar | Unknown | 10.83 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:cdKVhc8A:xcsV6rQo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cdKVhc8A:xcsV6rQo"
}

