Tags
Creators
Details
Licensed CC-BY-4.0
Published 6 months ago
Updated 5 months ago
All versions
0.1.0
Alpha
culiatum-rp 0.1.06 months ago 24
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Changes
0.1.0-alpha
Initial public alpha release of Culiatum RP for Fabric 1.21.11.
Added
- Combat tagging system with teleport command blocking during combat
- Support for blocking configured teleport-related commands such as
/tpa,/tpaccept,/tpdeny, and/spawn - Elytra flight disabling for combat-focused balance
- Recall Potion item that returns the player to spawn
- Brewing support for the Recall Potion from an awkward potion and a nether star
- Admin-controlled Radar item for bounty-style missions
- Radar target assignment with configurable mission duration
- Action bar radar feedback showing target distance
- Radar cooldown system
- Automatic radar expiration and removal when the mission time ends
Changed
- Combat tag default duration set to 15 seconds
- Radar flow now expects a single radar per player
- Radar assignment now requires the hunter to have a radar in their inventory
Combat Rules
- Player vs player damage tags both attacker and victim
- Hostile mob damage tags the player victim
- Hostile mob projectiles are also treated as combat triggers
- Passive mobs do not trigger combat tagging
Notes & Compatibility
- This is an alpha release intended primarily for the Culiatum server ecosystem
- Designed to work alongside Culiatum Economy and Essential Commands, but it is not required
- Not intended to be compatible with combat-tagging mods that provide overlapping functionality
Optional dependencies
Any compatible version
Any compatible version
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:zMLskhJT:QE0FOFl9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zMLskhJT:QE0FOFl9"
}

