All versions
0.3.0
Beta
Attuned Anchors 0.3.04 months ago 30
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client and server
Changes

Attuned Anchors 0.3.0
Initial Modrinth release.
Features
- Buildable Local Anchors and Global Anchors.
- Local anchors work within a configured nearby radius.
- Global anchors stay available from anywhere in the same dimension.
- Admin command spawning for local and global anchor structures.
- Anchor activation through item frames and configured anchor items.
- In-game N menu for anchor management.
- Admin teleport button in the N menu.
- HUD markers for visible anchors with distance display.
- Anchor rename, color, and icon customization.
- Large selectable marker icon set with categories.
- User access management through name tags.
- Public anchors using an unnamed/default name tag.
- Private anchors using named name tags.
- Users view showing assigned users, public status, or no-user state.
- Anchor deletion from the admin menu.
- Safe teleport placement near anchors to avoid landing inside blocks.
- Automatic anchor validation.
- Broken structures disable their anchor.
- Repaired structures reactivate automatically.
- Fully removed structures are cleaned from storage.
- Candle state feedback for active/inactive anchors.
- Persistent anchor storage across world/server restarts.
- Admin permission checks for menu, edit, delete, teleport, spawn, and despawn actions.
Technical Notes
- Combined client/server jar.
- Client and server are both required.
- Refactored systems for activation, validation, teleport, debug, storage, and UI rendering.
- Java source files are kept under 500 lines for maintainability.
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:ClrRuGLT:Yq3rYM63"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ClrRuGLT:Yq3rYM63"
}

