Tags
Creators
Details
26.11
Compatibility
Changes

Update 26.11 is here :
Discover now a large amount of content focused on the Palladium Alchemist, as version 26.11 is officially available, featuring the latest fixes, additions, and updates.
New content :
- Addition of Amethyst Portal, Titanium Portal, Paladium Portal, and Endium Portal
- Addition of flask & sap flask and tanks.
- Addition of Weighted Boots.
- Everything about Miner dimension !!!.
- Withered Obsidian
- Withered Piston (The method of obtaining it differs from that of paladium.)
- Extractor, can extrate sap of any modded logs
- Added Dead Wood.
- Added /furnace.
- Added crafting in the cauldron for birch water saplings.
- Added Birch Water Saplings, which function like paladium.
- NEW !! Paladium biomes are present.
- Added a command to modify pog levels, increase xp
- Added Magnet
- Added Unclaim Finder
- Added Endium Cave Block
- Added Hang Glider
- Addition of head drops when killed by another player
Modification !!
- Removed Corrupted dimension !!!!
- Redesign of the POG with its 100 levels (POG upgrade + minor fix).
- The amount of endium in the miner dimension has been modified
- Fixed ore generation
- Modification of modded ore textures in the deepslate version
- Adjustment to SHIFT CLICK IN THE CUSTOM INTERFACE (CRUSHER)
- Addition of Endium Fragment crafting
- Reduced the total drops from modded trees in boxes.
- Reduced drop rate of any modded sapplings
- Fixed Paladium Armor trim effect
bug fix !!
- fix 50/50 chance of obtaining an Endium Nugget in the Crusher
- fix many minor and major bugs
Thanks for playing
We thank you for your patience and support for the project and hope you enjoy the update.
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:pURl7B2k:N7RIJnnC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pURl7B2k:N7RIJnnC"
}

