Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 10 months ago
All versions
1.21.1-0.6.0-Beta
Beta
NeoBlock - The new OneBlock 1.21.1-0.6.0-Betalast year 61
Compatibility
Minecraft: Java Edition
1.21.1–1.21.4
Platform
NeoForge
Supported environments
Client and server
Changes
✨ New Features
- 🧰 Chests Config: Added
chests.tomlallowing custom chests with loot. Useneoblock:chest:<chest_id>in configs to spawn loot chests. - 🔄 Complete Tier System Rework: Now reloads all configs at world start instead of game start.
⚠️ Old worlds will break — back up your saves! - 🔗 Block Sequences: Define sequences with
neoblock:seq:<sequence_id>orneoblock:sequence:<sequence_id>to generate blocks in a specific order. - 🪨 Starting Blocks per Tier: Guarantee starting blocks (e.g., chests with tools) after unlocking tiers via tier configs.
- 📍 Configurable Block Position on Start: Control initial block placement through config.
- 🎲 First Block from Tier 0: Spawn point block is now chosen from tier 0's starting sequence or randomly from tier 0 blocks, replacing the default grass block.
- 🔧 Allow Any Preset: Use any preset, including the default world gen. Presets can be pre-selected in config during world creation.
- 🛠️ New Commands:
/neoblock force setblock <x> <y> <z>: Activate NeoBlock and set block generation position./neoblock force stop: Put NeoBlock in dormant mode, stopping generation until reactivated.
- 💪 Force Block in Presets: The
force-blockconfig forces block generation even with non-built-in presets. - 🎟️ Mob Trade Tickets: New item allowing players to request mobs from traders, replacing spawn eggs.
🐞 Fixes & Improvements
- 🦘 Fixed player “jump” glitch caused by teleport attempts while breaking blocks near edges.
- 🚫 Fixed trader message showing when no trader was present.
- 🌐 Fixed various translation message issues.
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:Wk2O53hD:UeZvtMPh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Wk2O53hD:UeZvtMPh"
}

