Tags
Creators
Details
1.1.0
Compatibility
Changes
Create: Totem Factory 1.1
What's New?
Quite a lot that's new actually!
A pretty big overhaul of the original mod,
forked from Mystic Creations Team's Create: Totem Factory - Postmortal and expanded in collaboration
with them to bring more content such as new resources, equipment, decorational stuff
and slightly rethought recipes to make automation a tiny bit more possible
Wider Loader & Version Support
Now officially on:
- Fabric, Forge & NeoForge
1.20.1 - NeoForge
1.21.1
(We're waiting for Create 6.0 for Fabric 1.21.1 before releasing C:TF 1.21.1 Fabric)
Resources
- Tumbaga Alloy
- It's an actual thing irl
- It's an alloy from about 400BCE mostly made into jewelry but also trinkets such as totems
Items, Tools & Armor
- Full set of Tumbaga Armor & Tools -Benefits of Gold with nearly the durability of Iron -Pretty useful early game if you get a heated mixer setup before full diamond
Blocks
- Block of Tumbaga Alloy
- Tumbaga Casing
Advancements
There's whole 7 new advancements, some funny references, some pretty hard and some pretty easy.
I can't be bothered to list them
- Millie
Recipes
- Replaced all Brass to Tumbaga Alloy in Totem parts' recipes
- Changed the End Crystal to a Ghast Tear in Totem Body recipe
- Still doing that healing factor, but more convenient
- Added Ghast Tear recipe
- Bulk haunting snowballs
Localization (Supported Languages)
- English US
- English UK/GB
- Russian
- German
- Polish
- Dutch
- Portuguese BR
- Spanish ES/AR/CL/MX/UY/VE
- French
- Italian
Bug Fixes / Technical Improvements
- Corrected Item Rarity for Totem parts (Common -> Uncommon)
- Corrected Item Stack sizes for Totem parts
- Incomplete Totem parts no longer appear in Creative menu
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:ae2lDuIP:usqucgFx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ae2lDuIP:usqucgFx"
}

