Links
Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
BRIDGES Judge v2.0.0 - Titancraft Season 11
New Features
Teams can now spend a move to block remaining open nodes on a floor they own. The mod detects blocked floors, counts the move toward the blocking team's total, and displays blocked floor numbers inline in the tower stats text
Circuits
Circuits are pre-built skulk block connections that any team can use to travel between floors. The mod detects circuit connections, includes them in path routing, and renders them in the team's path color.
Connection Intersection Detection
Bridges and circuits that physically cross each other are now detected and reported as errors, with a warning icon placed at the crossing point.
Warning Icons
Invalid connections now display a 3D warning icon in the world above the problem location in addition to the chat error message.
Tower Capture Bonus Scoring (S11)
Rules for tower capturescoring have been updated to match the Season 11 rules.
Changes
- Updated map layout: Tower color and height configuration updated for the Season 11 arena.
- Improved path visuals: Connection lines and dots are now rendered as 3D blockbench models with textures instead of flat primitives.
- Background scanning: World scanning now runs on a background thread, preventing the game from freezing during a rescan.
- Default coordinates updated to match Season 11 server placement.
- Team colors renamed to match Season 11 teams.
- Coordinates for the build on Titancraft are pre-set, so you no longer need to run
/bridges setCenterTower
Bug Fixes
- Fixed reversed width/height in world coordinate math.
- Fixed path validation incorrectly rejecting the base floor in some cases.
Internal
- Added unit tests for circuits, connection segments, connection validation, and tower scoring.
- Refactored connections to use a shared Connection sealed interface (Bridge, Ladder, Circuit).
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:lTeSKHmb:WUSQncfJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lTeSKHmb:WUSQncfJ"
}

