Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 6 months ago
All versions
1.7.1-neoforge-2.2.0
Release
Cobblemon Spawn Notification 1.7.1-neoforge-2.2.08 months ago 1,865
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Required content
Changes
- Moved from notifications directly associating with broadcasts to the new situations firing off themselves and other situations where necessary, and having broadcasts effectively listen for those situations.
- Added more direct coord_x/y/z, and dim_raw_path/namespace for more granular substitutions where necessary (waypoints).
- Moved from LazyRegistry to proper registries for parts and broadcasts.
- Changed destinations to broadcasts.
- Wrote so many codecs.
- Broke out conditions to their own entities and created a registry for them.
- Swapped out parts for the new segments in messages, with full registry support, so we can have reference and full segments.
- Added config options to disable situations, segments, and segments per situation(s).
- Removed ActionBarBroadcast, it's just the actionBar property on a ChatBroadcast now.
- Swapped segment lists for maps with index keys, as we may have segment additions target specific indices in a full segment going forward.
- Added a couple of map/list<->either extension functions for convenience.
- Added a MutableComponent.withPossibleStyling convenience extension.
- Added a default message template of placeholders for each segment for that message, including delimiter, before, and after functionality.
- Added SegmentAdditions to add new segments in existing full segments.
- Added the hatch trigger, and related data.
- Completely rehauled the data and lang file to match new schemas.
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:LPuJjiQz:TUxXZkGe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LPuJjiQz:TUxXZkGe"
}



