Tags
Creators
Details
All versions
1.5.0
Release
Tag Mod 1.5.04 months ago 26
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Changes
KILLER MODE WAS SUGGESTED BY @lixusthegreat ON DISCORD! https://discord.com/invite/BuScftvMKc
Changelog — v1.5.0
New Features
- Added Killer Mode — one Killer eliminates Runners by hitting them
- Added Normal Mode command (
/tag config normalMode) to switch back to classic tag - Eliminated players in Killer Mode are teleported 2–5 blocks away from the Killer to spectate safely
- Round automatically restarts with a 5 second countdown if the Chaser/Freezer/Killer leaves mid-round
- If not enough players remain to restart, the round is cancelled with a message
Improvements
- Big screen title messages now show on round start for all players
- Coloured glowing outlines per role (red for Chaser/Killer, aqua for Freezer, green for Runners)
- Freeze timer reduced from 60 seconds to 15 seconds
- Frozen players now see a countdown on their screen: "You will become a freezer in: Xs"
/tagstartand/tagstopnow show who started/ended the round in chat- Switching modes automatically disables the previous one
- Round end now shows the longest surviving Runner and their survival time
- All frozen players are freed and ice cages are removed when
/tagstopis used
Bug Fixes
- Fixed Chaser hitting Runners doing nothing in Normal Tag mode
- Fixed big screen titles never appearing
- Fixed
/tagstopalways saying "Round Ended" even when no round was running - Fixed glowing outlines being white instead of coloured
- Fixed Killer Mode round ending showing "Round Ended" twice in chat
- Fixed frozen players getting softlocked with no way to escape
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:EUY3r7JM:SoWgKPrz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EUY3r7JM:SoWgKPrz"
}

