1.0.0
Compatibility
Changes
Contagion Signal
Inspired by AltarSMP.
Base item: Echo Shard
Command: /contagionsignal [player]
Permission: customweapons.contagionsignal (default: op)
Resource Pack: Install the AltarSMP Texture Pack - this plugin set is built around it and looks/sounds as intended with it installed.
Cross-Plugin Detection (/weapons)
Every AltarSMP weapon plugin registers /weapons [player], which hands you one weapon from every other AltarSMP plugin currently installed and enabled - a live check each run, nothing to configure.
Crafting Recipe
. E .
G E G
. R .
Where:
E= Echo ShardG= Gold IngotR= Redstone Block
Drop the ingredients into a crafting table in that pattern (. = empty slot) to get the Contagion Signal. Recipe can be turned off in config.
Enchantments
- Mending I
Not a melee weapon, bow, or armor piece, so it doesn't carry combat/defensive enchantments beyond Mending. Still unbreakable.
config.yml
weapon:
cooldown-ability-1: 40
cooldown-ability-2: 0
recipe:
enabled: true
shape:
- " E "
- "GEG"
- " R "
ingredients:
E: ECHO_SHARD
G: GOLD_INGOT
R: REDSTONE_BLOCK
Cooldowns are in seconds and reload from config on server start. Set recipe.enabled: false to disable crafting and hand the item out with /contagionsignal only.
Abilities & Triggers
| Trigger | Ability | What it does |
|---|---|---|
| Right-Click | Pale Curse Beacon | Summons a floating beacon at your feet that pulses Poison to nearby entities over its duration, then disappears. |
| Shift+Right-Click | (none) | This weapon has no secondary ability. |
Notes
- The weapon is bound to the player who receives it via a persistent NBT tag, so lore/name changes won't break ability detection.
- The activating player is never hit by their own ability's damage, knockback, or negative effects, even for area attacks, explosions and travelling projectiles/waves.
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:FWXr1xzk:ALVmUIyi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FWXr1xzk:ALVmUIyi"
}

