1.0.6
Compatibility
Changes
Bricksanity - (Update 1.6)
- Added Glowstone Dust Brick
- Added Vilegourd Brick
- Added Carved Vilegourd Brick
- Added Shrill O' Lantern Brick
- Added Ribs Brick
- Added Brickhaunter (new workstation)
- Added Soul Sprite
- Added Soul Biomass [might change the name]
All bricks and items are obtainable in this update!
Bugfix Patch Required
The Brickhaunter doesn't currently work and recipes may not actually be functional yet, so please update as soon as you see 1.0.6.1 as that'll be the bugfix patch to fix all current issues. Along with making it so you can actually get the Brickhaunter.
Other Additions in this update
Glowstone Bricks can nolonger be directly made from the Brickversion Station and now require 4 Glowstone Dust Bricks to make, this makes it a bit easier to make as you don't need the glowstone block anymore.
Brick Haunting is a new addition that may get updated in the future to be less dependant on the button being pressed to make stuff, it'll take time but it'll be worth the wait I hope.
Most of the bricks require the Brickhaunter, but just know the conversions are pretty straightforward, except for the Soul Sprites, which actually requires soul sand and shears to get the soul sprites required, this is how you extract the soul bricks from soul sand bricks, giving you some soul sprites back in return.
Whenever you brick haunt something in the Brickhaunter, it'll produce a bit of soul biomass as a result, this is a trash item that might get bricks of it and decorative blocks later on, but one thing to note is that the heavier the cost of the object/the more soul energy it takes, the more soul biomass can be produced.
Next Update might include;
New Brick mechanics for getting specific bricks. More spooky bricks which have unique ways of obtaining them.
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:Cj3cRQcA:tSfhfsT7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Cj3cRQcA:tSfhfsT7"
}

