Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 years ago
All versions
0.0.1.7-1
Release
0.0.1.7-12 months ago 14
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
v0.0.1.7-1 | commit 9f5ed14
- Abandoned Altar structures now generate in Mana Plains biomes. Four variants exist: heavily damaged structures appear frequently on smaller terrain patches, while more intact but still ruined versions appear less often on larger Mana Plains. Variant 04 contains a chest with mana materials.
- 廢棄祭壇結構現在會在魔力草原生物群系中生成。共有四種變體:高度損毀的版本在較小的魔力草原地形頻繁出現,而較完整但仍損毀的版本則在較大的地形低機率出現。變體 04 含有一個裝有魔力材料的箱子。
- Added three ruin decoration blocks: Cracked Mana Bricks, Mossy Mana Bricks, and Ruined Mana Pedestal. These appear in abandoned altar structures.
- 新增三種廢墟裝飾方塊:裂紋魔力磚、苔蘚魔力磚和損壞的魔力底座,出現在廢棄祭壇結構中。
- Mana Grass Block now correctly drops Mana Soil when mined without Silk Touch.
- 魔力草方塊在不使用精準採集時現在能正確掉落魔力泥土。
- Fixed Mana Deployer and Resonance Ring not being mineable with a pickaxe.
- 修正魔力部署器和共鳴環無法用鎬子挖掘的問題。
- Added Nara Guide, accessible via the Guide tab in the Nara Watch screen. Covers four chapters: Aspect System, Research System, Mana Facilities, and Altar System.
- 新增娜拉指引,可透過娜拉手錶介面的指引頁簽開啟,涵蓋四個章節:本源系統、研究系統、魔力設施、祭壇系統。
- Added advancement for crafting the Research Table.
- 新增合成研究台的進度成就。
- Added Consensus Glasses: binds to the first player who uses it, snapshotting their research and aspect data. Other players can use the item to copy that knowledge to themselves.
- 新增共識眼鏡:第一位使用的玩家將其綁定並快照研究與本源資料,其他玩家使用後可將該知識複製至自身。
- Added Source Tome: unlocks all research, sets research tier to 12, and grants 500 points of every aspect. No crafting recipe; intended as a late-game or creative tool.
- 新增源典:解鎖全部研究、將研究階段設為 12,並賦予每種本源 500 點,無合成配方,定位為後期或創意模式工具。
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:x9pJj8Sv:1cSMQMxn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:x9pJj8Sv:1cSMQMxn"
}

