All versions
1.3.0+26.1.2
Release
Liteminer Extra Shapes 1.3.0 Neoforge4 months ago 158
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client-side
Changes
Liteminer Extra Shapes v1.3.0
🆕 What's New
- Selection HUD: The Selection pattern now shows "0 blocks selected" above the crosshair before you've picked both points, instead of staying silent like before.
- NeoForge Support: Liteminer Extra Shapes is now also available for NeoForge, alongside Fabric — same patterns, same menu, same keybinds.
🔧 Improvements & Fixes
- Liteminer 26.1.2 Support: Migrated to Liteminer's new public Addon API (
LiteminerShapes) — the old internal shape list was removed in 26.1.2, which caused the mod to crash on startup with recent Liteminer builds. Fixed.
Version Support
- Added official support for 26.1.2.
- Fabric: requires Liteminer 3.1.0+26.1.2+, Fabric Loader 0.19.0+, Fabric API 0.153.0+26.1.2+.
- NeoForge: requires Liteminer 3.1.0+26.1.2+, NeoForge 26.1.2.76+.
Liteminer Extra Shapes v1.3.0 (RU)
🆕 Новое
- HUD для Selection: Режим Selection теперь показывает надпись «выбрано 0 блоков» над прицелом ещё до выбора обеих точек, а не молчит как раньше.
- Поддержка NeoForge: Liteminer Extra Shapes теперь доступен и для NeoForge, не только для Fabric — те же паттерны, то же меню, те же клавиши.
🔧 Улучшения и исправления
- Поддержка Liteminer 26.1.2: Переход на новый публичный Addon API Liteminer (
LiteminerShapes) — старый внутренний список фигур убрали в 26.1.2, из-за чего мод крашил игру при запуске на свежих сборках Liteminer. Исправлено.
Поддержка версий
- Добавлена официальная поддержка 26.1.2.
- Fabric: требуется Liteminer 3.1.0+26.1.2+, Fabric Loader 0.19.0+, Fabric API 0.153.0+26.1.2+.
- NeoForge: требуется Liteminer 3.1.0+26.1.2+, NeoForge 26.1.2.76+.
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:B0oEYDNC:qNJSxQWM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B0oEYDNC:qNJSxQWM"
}

