Links
Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated last year
All versions
1.0.0
Release
Cosmicore 1.0.0 [1.21]2 years ago 9,287
Uploaded by
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog 1.0.0 (Meteors, new Material and more!)
Items
Titanium
- reduced the Knockback Resistance of the armor to 9% from 10%
- added horse armor for this material
Lonsdaleite
- new material extracted by crushing Pallasite
(Lonsdaleite) Smithing Template
- new Smithing Template to update your Diamond gear into Lonsdaleite gear (found in the Meteor Sites instead of Titanium Smithing Templates)
Meteorite Banner Pattern
- new vannilaish banner pattern based on our mods icon (found in the Meteor Sites)
Blocks
Infernium Block
- the infernium block can be used as fuel in the Crushers just like infernium but counts as the crafting materials! (but you can't uncraft it)
Machines
Crushers
- now you can see the amount of Ignis in the crusher
- now the bar can have a max number of 44 crushes (so 4 infernium crystals can be stored in a crusher max)
- now the Advanced Crusher renders both Ingredient Slots
- now the Crushers renders when joining a world again (this also fixes the multiplayer rendering so now players can see if the crusher is used by another player)
- new Ignis Bar texture and new GUI texture therefore
Meteor Shield
- new block that shields meteor impacts (based on tiers)
Meteors
- added the first 2 meteors, the Achondrite and Meteorite, able to spawn in the Overworld (as meteors should)
Extra
- added a new Gamerule for allowing meteors to spawn
Fixes
- now the Titanium Crossbow is craftable
- Advanced Crusher crashing the game if output slot is full (rookie mistake)
Other
- Updated NeoForge version to 21.1.80
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:I6sYca4V:HcXyxGAt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:I6sYca4V:HcXyxGAt"
}

