Tags
Creators
Details
0.1.219-mc26.3+neoforge
Compatibility
Changes
Changelog
0.1.219

Homes and roads for the ALA work towns: drones restore the ruined houses and build new ones by plan, a town road network carries power to every house, and shift workers get a home with a charging bed.
New
- Town Road, a walkable grate block with an insulated wire inside that carries power. Drones lay the town's road network from the town hall, and a building counts once its inlet shares a network with the core.
- Shift workers now live in capsule houses. The first homeless worker moves into a restored house and charges on its bed, and the Reception Capsule only brings a worker back when a free house waits.
- New house blocks: the House Inlet, which takes power only on its outer face, and the two-block Charging Bed a shift worker lies down on to charge.
- Lay a new house anywhere in a town's territory: place a House Inlet, pick a plan and a turn. The site is checked, then drones clear it, lay its road and build it.
- House Plans: a town learns each of the four house types once, from a sheet put into the dispatcher or used on the core. Sheets lie in house ruins or are crafted, and the town hall gives one.
Improved
- The Settlement Core's Construction tab shows building cards with progress bars and a hint for the next step. A Find button outlines a shift worker through walls, and town chat lines are coloured.
- Builder drones open wooden doors, trapdoors and gates on their way and shut them behind, place doors and beds whole and clear grass and flowers themselves.
- The Town Dispatcher keeps a queue of orders for chosen buildings that you can reorder or cancel. When a job stops, the reason is shown in the window and said once in chat.
- Shift workers move like people in heavy suits: a weighty walk, breathing while they stand and a wave to greet you.
Bug Fixes
- The Town Dispatcher window now fits on a 1280x720 screen at GUI scale 3.
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:ACLWFBlU:dtrjSLmz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ACLWFBlU:dtrjSLmz"
}

