Creators
Details
1.2.0
Compatibility
Changes
What's New
v1.2.0
NOTICE: Please do not expect existing custom triggers to work with this version, update them accordingly. See wiki for updated values
New trigger system
Triggers are now much more flexible and is no longer tied to just entities, thus the path has changed from smb_entities to smb_triggers
Here is an example of the new trigger file:
{
"type": "entity_died",
"target_entities": [
"minecraft:ender_dragon"
],
"display_mode": "dimension",
"style": "souls_message_banners:dragon_felled",
"priority": 1
}
Trigger Types: type
entity_died- After an entity diesentity_spawned- After an entity spawnsplayer_died- After a player diesplayer_spawned- After a player spawnsplayer_set_spawn- After a player set a new spawn pointblock_state_changed_on_interact- After a block changes state when player has interacted with itwaystone_activation- After a waystone has been activatedbonfire_lit- After a bonfire has been litraid_status- After a raid has ended
Trigger Targets:
target_entities- For types that utilize entitiestarget_players- For types that utilize playerstarget_blocks- For types that utilize blockstargets- For special types such as raid status
Trigger Conditions: conditions
This are conditions that can be used on certain trigger types
- Entity related triggers
- killer
- apotheosis_rarities
- Blockstate related triggers
- new_blockstate
- old_blockstate
Trigger Display Mode: display_mode
This determines which players will see the message banner.
all_playersdimensionradius
Client Config
Banner Play Mode
EVERYTIME- Play banners everytime it has beeen triggeredONCE_A_WORLD- Play banners just once during a world sessionONCE_A_SESSION- Play banners just once the entire game session
Trigger blacklist
Clients can now block certain trigger types from appearing through the config in <namespace>:<trigger_id> format.
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:hx4Rlnhh:YEe0rtpz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hx4Rlnhh:YEe0rtpz"
}

