
Empyreum SMP
Empyrm Weapons adds powerful mythological weapons inspired by Greek gods to the Empyrm SMP — a scripted Minecraft server centered around divine kingdoms, corruption, and legendary combat. Wield weapons blessed by Zeus, Hades, Artemis, Ares, Hephaestus, and
1.1.0
Compatibility
Changes
⚔️ EMPYRM WEAPONS v1.1.0 ⚔️
This update focuses on expanding weapon functionality and improving gameplay balance while preparing the system for future content.
━━━━━━━━━━━━━━━━━━━━ ✨ New Features ━━━━━━━━━━━━━━━━━━━━
• Added Weapon Abilities Each divine weapon now includes unique abilities tied to its godly origin. These abilities enhance combat and begin defining the identity of every weapon within Empyrm SMP's mythology.
• Weapon Descriptions All weapons now contain in-game descriptions explaining their purpose, power, and general behavior. This helps players understand how each divine relic functions.
━━━━━━━━━━━━━━━━━━━━ 🛠️ Improvements & Fixes ━━━━━━━━━━━━━━━━━━━━
• Spear Balance Fix The Spear has been reworked and fixed after being excessively overpowered. Combat performance and usability have been improved for better gameplay balance.
━━━━━━━━━━━━━━━━━━━━ 🎨 Visual Development ━━━━━━━━━━━━━━━━━━━━
• Custom Textures (Coming Soon) Weapons currently use default visuals. Custom textures and models are planned for future updates to better represent their divine origins.
━━━━━━━━━━━━━━━━━━━━ 🔮 What's Next ━━━━━━━━━━━━━━━━━━━━
This update lays the foundation for upcoming features, including:
• More abilities • Expanded weapon mechanics • Custom textures & models • Additional mythological content • Continued balancing and polish
More updates coming soon as Empyrm SMP continues to evolve.
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:407BEjTN:1VDiFHC4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:407BEjTN:1VDiFHC4"
}
