All versions
2.0.0+mc26.1.2
Release
SignPort 2.0.0 for Minecraft 26.1.22 months ago 10
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
- Added client-side SignPort helpers when both client and server have SignPort installed: synced anchor/permission data, HUD lookup hints for portal signs, the anchor browser, sign-editor autocomplete, and a permission-gated SignPort Template form.
- Added the SignPort anchor browser on the default
Jkeybind, with dimension tabs, search, name/distance/recent sorting, collapsible group sections, and synced-cache teleport actions. - Added portal sign editor autocomplete and the SignPort Template form to make valid portal signs easier to create from the synced anchor cache.
- Added tab-completion of anchor names for
/sp tp <name>and/sp anchor delete <name>. - Added paginated
/sp anchor list [filter] [page], clickable previous/next navigation, configurableanchorListPageSize, and case-insensitive filtering. - Added optional anchor groups via
/sp anchor create <name> <group>and/sp anchor setgroup <name> <group>, with grouped list output and group-name tab-completion. - Added
/sp anchor near [radius],defaultNearRadius, and/sp anchor list --sort=name|distance|recent. - Added optional BlueMap integration for publishing anchors as map markers, controlled by
bluemapEnabled. - Added startup anchor summary logging and eager legacy file migration.
- Added release/docs hygiene improvements, including Modrinth description sync, listing validation gates, workflow/source hygiene fixes, and stale
ResourceKey.location()checks. - Updated Modrinth publishing to use the
signportproject slug.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| signport-2.0.0+mc26.1.2-sources.jar | Unknown | 44.62 KiB |
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:9sAIhwXX:oUTTWy3m"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9sAIhwXX:oUTTWy3m"
}

