1.0.1-beta
Compatibility
Changes
Shard's Factions — v1.0.1-beta Initial release. First public build. Early release, active development — expect changes. Requires installation on both client and server. Core
Native NeoForge faction system for Minecraft 1.21.1 / NeoForge 21.1.230 — works with modded block-breaking and explosions, not against them. Claim protection: non-members cannot break or place blocks in a protected claim. Hand tools and automated miners are blocked — explosives are the only way through.
Factions
Create, disband, invite, join, leave, and kick. Three-rank hierarchy: Owner / Officer / Member, with per-command permission gates. Owner-only promote/demote with directional guards; ownership transfer; ownership never left vacant. Invite-gated membership with expiring invites.
Claims & Power
Chunk claiming against a member-scaled power budget. Combat-driven power: PvP kills shift power between factions. Overclaiming — stronger factions can peel territory from overextended rivals, self-limiting as the attacker's own commitment grows. Autoclaim and unclaim.
The Obelisk
Custom block that anchors a faction's protection. Breakable by any player (hand, tool, or explosive) but immune to automation. Destruction drops protection and notifies the owning faction's online members. Configurable acquisition cooldown (default 1 week); destroyed on holder death.
System Zones
Admin-created SAFEZONE (no PvP, fully protected) and WARZONE (PvP live, blocks protected); both explosion-immune and permanent. Admin command suite for system-zone setup.
Quality-of-Life
Permission-gated chat-grid claim map. Action-bar territory display on border crossings. Faction-home teleport to the Obelisk.
Permissions
NeoForge native permission system — standalone, with optional LuckPerms (or any manager) integration. No hard dependency.
Notes
Server-side authoritative; all faction data persists across restarts. For explosive-heavy packs, see the companion Shard's Factions — Ballistix Compat.
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:bSoJoPxM:WV3UD9p2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bSoJoPxM:WV3UD9p2"
}

