Tags
Creators
Details
Licensed GPL-3.0-only
Published 8 months ago
Updated 5 months ago
All versions
1.1.5-Alpha
Alpha
BlockZ 1.1.5-Alpha7 months ago 495
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
1.1.5-Alpha
1. Item Grid System: In-Game Real-Time Editing Persistence Synchronization
- New Command:
/blockz_grid_item <width> <height> [color] - Modify the global grid rules of the item in your main hand (
width/height) coloris optional: supports0xAARRGGBB/#RRGGBB/#AARRGGBB- If
coloris not provided: clears the custom color of the item and reverts to the default color - Changes will be written back to
config/blockz/grid_items.jsonand synchronized to all clients immediately - New Command:
/blockz_clothing_capacity <width> <height> - Only usable when the main hand holds clothing ([ClothingItem])
- Modify the internal grid capacity of clothing/backpacks:
cap_width/cap_height(total capacity =width * height) - Changes will be written back to
config/blockz/grid_items.jsonand synchronized to all clients immediately
2. DayZ Zombie System (Added to 1.1.5 Summary)
- DayZ Zombie Entity:
blockz:dayz_zombie - Registers entity, attributes, and spawn egg (
dayz_zombie_spawn_egg) - Includes corresponding resources: models/animations/textures/loot tables, etc.
- Naturally spawns in the main world
- Via Forge
biome_modifier: - File: [data/blockz/forge/biome_modifier/add_dayz_zombie_spawns.json]
- Injects zombie spawns into
#minecraft:is_overworld(weight=28,minCount=1,maxCount=3) - Natural Spawn Toggle
- Controlled via
DayZZombieConfig.enableNaturalSpawn - When disabled, intercepts
NATURAL/CHUNK_GENERATIONspawns (keeping spawn eggs/commands and other non-natural spawns)
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:5V4U9QIJ:uloJlDMH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5V4U9QIJ:uloJlDMH"
}

