Links
Tags
Creators
Details
v2.8.0
Compatibility
Changes
This update introduces the Colossus Architecture, a monumental evolution in property governance.
Designed for high-performance environments, v2.8.0 transforms property security from a simple lock into an autonomous, state-driven "Fortress" that lives within your world.
โจ ๐ข ADDED (3)
- Keys Command โ A new command has been added: "Keys". This command shows you your properties.
- Double Chest Support โ The system now supports double chests.
- Colossus State Engine ๐ก๏ธ โ Weโve moved beyond static locks. The new engine handles thousands of property states via an Asynchronous Maintenance System, ensuring absolute TPS stability even on the most populated servers.
๐ง ๐ก IMPROVED (3)
- Industrial Integrity Layer โ๏ธ โ Full, native support for Barrels, Crafters, and Smelting Units. These blocks now feature "Smart-Automation Logic," allowing Hopper compatibility while maintaining an unbreakable seal.
- Smart-Inventory Extraction ๐ โ When a container is reclaimed, its contents are routed directly to the player's inventory, preventing theft and loss in crowded areas.
- Dynamic Retention Model โ๏ธ โ Protection timers now adapt to player activity. Featuring a "Trust-Based Extension," shared property remains protected as long as any trusted member is active.
โจ ๐ฃ NEW (2)
- Unified Chest Binding ๐ฆ โ Double Chests and side-by-side placements are now treated as a Unified Molecular Entity. If one side is secured, the entire structure is impenetrable.
- Expire Station Protocol ๐งน โ An automated 7-minute world-validation cycle that detects and purges orphaned data, keeping world files lean and preventing ghost lock clutter.
๐ ๐ต FIXED (1)
- Metadata Recalibration ๐ฐ๏ธ โ Resolved edge-case desync issues involving Ender Chest interactions and cross-chunk persistence errors during high-load periods.
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:qa8G3unK:UnfK6rsX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qa8G3unK:UnfK6rsX"
}

