Tags
Creators
Details
0.1.1-SNAPSHOT
Compatibility
Changes
0.1.1-SNAPSHOT
Added URI-based notice importing for cases where notice content is too large or too inconvenient to enter directly through chat commands.
Added
Notice Import
- Added
/angello import <uri>for publishing a notice from an external file source. - Added import subcommand aliases:
/angello uri <uri>/angello import-uri <uri>/angello send-uri <uri>
- Added support for importing notices from local file paths,
file://URIs, andhttp(s)://URIs.
Import Format
- Added JSON-based import format for external notice definitions.
- Added support for required fields:
titlebody
- Added support for optional fields:
lifetimecreated_bycreated_at
- Added support for
bodyas either:- a single string
- an array of strings
- Added support for
created_atas either:- a formatted date-time string
- a timestamp
Import Behaviour
- Added import handling that converts external notice data into a normal stored notice.
- Added fallback to
settings.default-notification-lifetimewhen imported notices do not provide alifetime. - Added fallback to the command executor as
created_bywhen the imported file does not provide it. - Added fallback to the current time when
created_atis omitted. - Added validation for malformed or incomplete imported notice data.
Integration
- Added full integration between imported notices and the existing notice board system.
- Added imported notices to the same shared global history used by manually sent notices.
- Added stable global ID assignment for imported notices.
- Added immediate preview delivery for imported notices to eligible online players.
- Added support for imported notices in existing unread, read, lifetime, inbox, show, list, and delete flows.
Notes
Imported notices are not treated as a separate notice type. Once imported, they behave exactly like notices created through /angello send, including persistence, player read state tracking, lifetime handling, and administrative management.
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:EDRGfHSm:5UCi4ESw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EDRGfHSm:5UCi4ESw"
}

