18.1
Compatibility
Changes
Bedrock Stuff Update 18.1 (18.1_42 for 1.12.2):
Notes:
"L(a)gacy", (A Bedrock block model for Bedrock Stuff is W.I.P (kinda)), (I will not make a Update 18.1 variant for NF 1.21.4 because of the low demand on Curseforge and Modrinth)
-
Config/Features:
-
Added:
-
Added a new config category named "BS Legacy" (Not 1.12.2/FB 1.21.8/NF 26.1.2)
-
(This moves the "Reactor Core (BS Legacy)" config to this category and 3. adds also a new config option!)
-
The Config option "Border Block (BS Legacy)" (Not 1.12.2/FB 1.21.8/NF 26.1.2)
-
Changed:
-
The Border Block generates now a real border above the block to the build limit!
-
(The Block needs now the sky to work (because griefing protection if the border placed))
-
The Underwater Torch has now the right model of a torch!
-
The Underwater Torch has now other particles! (1.18.2+)
-
The Underwater Torch renders now a bit different, for more perfomance! (1.12.2)
-
You can now obtain the Elements "19" "58" "74" and "80" in the Element Constructor (1.12.2)
-
Items/Blocks:
-
Added:
-
Red/Green/Purple/Blue Torch:
-
From the Education Edition is this here a new decoration!
-
Cerium/Mercuric/Potassium/Tungsten Chloride:
-
Can be used to craft the new torches!
-
(All new Items/Blocks are instantly compatible with the MVS V1.17.X Present)
-
Commands:
-
Changed:
-
The "armorarms" command can now summon the "Armor Stand with Arms" in 4 rotations! (1.18.2+)
-
The "armorarms" command is now modifired with "_90" "_180" "_270" for the rotations (/armorarms_90)! (1.12.2)
-
Bugfixes and co.:
-
The Config "Reactor Core (BS L(a)gacy)" has been changed to "Reactor Core (BS Legacy),
-
The Underwater Torch dosn´t have the right "Light output" (1.12.2)
-
Added Support for 26.1.2 (Based on a 1.21.8 NeoForge and 1.21.8 Fabric hybrid with Game Rules!)
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:JFawZiqx:OIZWjndp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JFawZiqx:OIZWjndp"
}

