Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated 8 months ago
All versions
0.0.7
Release
Fayaz's Lockout 0.0.710 months ago 22
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Changes
Major Overhaul
Renamed
- "Death Lockout" ā "Fayaz's Lockout" (now supports multiple game modes)
Added
New Game Modes:
- Kills Mode: Race to kill unique mob types
- Death Mode Submodes: SOURCE (damage type) or MESSAGE (death text)
Game Start:
- 3-second countdown with player freeze (3, 2, 1, GO!)
- Players teleported to spawn point
- Inventories cleared, health/hunger restored
Spawn Points:
/lockout spawnpoint [x y z]- Set custom spawn (or use current location)- Defaults to world spawn if not set
Pause System:
- Auto-pause when participating player disconnects
- Title screen shows who to wait for
- Auto-resume on rejoin
- Manual controls:
/lockout pauseand/lockout unpause
Player Management:
- Default color assignment (color now optional when adding)
- Color uniqueness enforcement (no duplicate colors)
/lockout player modify <player> <color>- Change colors/lockout player remove <player>- Remove players
HUD:
- Pause indicator with title overlay
- Mode display (Deaths/Kills)
Changed
Command Structure:
/lockout addā/lockout player add <player> [color]/lockout mode <kills|death> [source|message]- Configure mode separately/lockout start- No longer requires mode parameter (uses pre-configured)/lockout stop- Ends match but keeps config/lockout reset- Wipes everything- Configuration persists between matches (until reset)
Status Command:
- Now shows: active/paused state, mode/submode, goal, players with scores
Fixed
- More reliable death tracking with SOURCE mode
- Prevents color conflicts
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:2wlS2VcS:fPgGW4pM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2wlS2VcS:fPgGW4pM"
}

