Links
Tags
Creators
Details
0.1.0
Compatibility
Required content
Changes
Changelog
All notable changes to this project will be documented in this file.
This project follows Semantic Versioning.
[Unreleased]
[0.1.0] - 2025-12-09
Added
-
Initial public alpha release of Decrees of the Six.
-
/decreesroot command with subcommands for council and decree management. -
Council seat system defined in
config/decrees/council.json:- Each seat has an
id,displayName, and optionalholderUuid.
- Each seat has an
-
Global council flags in
council.json:decreesEnabled– master switch to enable/disable the decree system.opsOnly– when true, only server operators can create/open/delete/vote on decrees.
-
Decree lifecycle:
- Create decrees with
/decrees decree create <title>. - Inspect decrees with
/decrees decree info <id>. - List all / own / active decrees:
/decrees decree list/decrees decree list my/decrees decree list active
- Edit fields via
/decrees decree edit title|description|category|expiry. - Open decrees for voting with
/decrees decree open <id>. - Delete decrees with
/decrees decree delete <id>(council only).
- Create decrees with
-
Voting system:
/decrees vote <id> yes|no|abstainfor council seats.- Voting rules configurable in
config/decrees/voting_rules.json:minQuorumPercentvotingDurationMinutesmajorityMode(SIMPLEorTWO_THIRDS)tiesPass(true/false)
- Automatic resolution to
ENACTEDorREJECTEDwhen:- Quorum is reached and
- Either all active seats have voted or the voting duration has expired.
-
Operator safety tools:
/decrees decree force <id> enacted|rejectedto override decree status (ops only)./decrees reloadto reloadcouncil.jsonandvoting_rules.jsonlive.
-
Council utilities:
/decrees seat list– list all seats and their current holders./decrees seat set <seat_id> <player>– assign a player to a seat (ops only)./decrees seat clear <seat_id>– clear the holder of a seat (ops only)./decrees decree results <id>– detailed results: yes/no/abstain, quorum status, timer./decrees decree list active– shows all decrees currently inVOTING, including your own vote if you hold a seat.
-
Basic decree history logging:
- Finalised decrees (
ENACTED/REJECTED) are written to a plain-text history log viaDecreeHistoryLogger. - Intended for season/roleplay records (e.g.
config/decrees/decrees_history.log).
- Finalised decrees (
Changed
- N/A – initial release.
Fixed
- N/A – initial release.
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:3BKuIrM2:TYmEZqMq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3BKuIrM2:TYmEZqMq"
}
