All versions
1.0.4-pre-6
Beta
Pathfinding Edition for MineColonies 1.0.4-pre-68 months ago 206
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Server-side
Client and server
Changes
前置依赖(Dependency)
minecolonies_version=1.20.1-1.1.1010-snapshot
更新日志
- 修复轮作计时多次计时的bug
- 农田将支持几乎所有类型的农田,各个tag功能细化
additional_seeds: 用以存储殖民地原版不支持的种子no_farmland_seeds: 用以存储无需耕地的种子underwater_seeds: 用以存储需要种植在一格深水中的种子
- 增加特殊农田映射,可以自由编辑特殊种子和对应的特殊农田,结构见
data/colonypathingedition/farmland_mapseed: 特殊种子,如果种子和农田都读取成功,将自动添加到农田的种子列表中farmland: 特殊农田,农夫在种植特殊种子时会请求特殊农田,特殊种子只会种植在特殊农田上
- 所有支持的农田都支持自动创建农田
- 进一步更新农民AI,现在农民工作会更有效率
- 更新普通作物(除殖民地作物)的沃土耕地兼容
- 补充更新日志开关,可以关闭游戏内更新提示(此版本默认关闭)
changelog
- Fixed crop rotation timer being triggered multiple times
- Farmland now supports almost all types of farms with more detailed tag categorization:
additional_seeds: Stores seeds not originally supported by MineColoniesno_farmland_seeds: Stores seeds that do not require farmland to plantunderwater_seeds: Stores seeds that must be planted in 1-block-deep water
- Added special farmland mapping, allowing customizing special seeds and their corresponding special farmland
(seedata/colonypathingedition/farmland_map):seed: Special seed; if both seed and farmland are loaded successfully, the seed will be added to that farmland’s seed listfarmland: Special farmland; farmers will request this farmland when planting special seeds, and such seeds will only be planted on their mapped farmland
- All supported farmland types now support auto-generation
- Further improved Farmer AI for more efficient work cycles
- Improved compatibility for rich soil farmland with normal crops (non-MineColonies crops)
- Added update-log toggle; you can now disable in-game update notifications (disabled by default for this 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:UFGyxCZm:9sdSx0S7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UFGyxCZm:9sdSx0S7"
}

