Tags
Creators
Details
ALPHA-2.0-P3
Compatibility
Changes
Prerelease. The third pilot of the 2.0 realism update: humidifiers, a config.yml that keeps up with new settings, cheaper signs, and a thermostat power switch. Same save format as Pilots 1 and 2 (format 6), so it's a drop-in upgrade. See the Pilot 1 notes for everything 2.0 adds.
Humidifiers
/hvac create humidifier [label]
- Build: put a waxed cut copper slab (bottom half) on top of an iron block, put a sign on the side of the iron block, and run the command while looking at the sign.
- What it does: adds moisture to the room of the system around it, or to its own zone anywhere else. It has the same 30-block reach as a dehumidifier.
- When it runs: it starts 2% below its setpoint and runs up to it. Click the sign to step the setpoint (30–50%), and sneak-click it to switch it on or off.
- Plumbed: it never runs dry and needs no refilling.
- While it runs: the slab fills with water and bubbles like water over soul sand. The water never spills, and a bucket can't take it.
Your config.yml keeps up
- New settings are added on startup. Anything added since your
config.ymlwas written appears in it, with its comments. A server upgraded from 1.x finally getshud:,weather:,humidity:,dehumidifier:,humidifier:and the pool target lines. - Your own values are never changed, even where a default has since changed.
- Backup: the previous file is kept as
config.yml.before-ALPHA-2.0-P3.bak. Aconfig.ymlthat can't be read is left alone.
Thermostat power switch
Sneak-right-click a thermostat sign to switch its system off (the sign shows System off), and again to switch it back on. This needs ezvac.use. Units you switched off on their own stay off, and a plain click still edits the target.
Signs are cheaper
- Only nearby signs update. Signs more than about 64 blocks from every player keep their last text, then update within a second of someone coming near.
- Nothing else changes: the simulation, equipment, saving and readings carry on exactly as before.
- Why: rewriting signs was EZvac's biggest single cost on large servers.
Fixed
A thermo-hygrometer placed without a label showed Thermohygromete on its sign. It now shows T. Hygrometer, including on signs you already have.
Verified
- Automated tests: 176, including the config update against a real 1.7-era
config.yml. It added 85 settings, changed none of the existing values, and a second run added nothing. - Live, on Purpur 1.21.1:
- Humidifier: it raised a dry heated room from 33% to its 40% setpoint and held it there. It bubbled, never leaked, and was removed cleanly when a part was broken.
- Config: the 1.7-era config was updated on startup, with its values unchanged.
- Signs: a distant sign stayed frozen, then caught up within 2 seconds of a player walking up.
- In-game: tried before release.
Upgrading
Stop the server, replace the EZvac jar with EzVac-ALPHA-2.0-P3.jar, and start it again. Your config.yml gains any missing settings on that first start.
From Pilot 1: if your config.yml already had a dehumidifier: section with range: 12, it keeps that value. Change it to 30 (and maximum-cells to 50000) to get the longer reach from Pilot 2.
The jar below was built by GitHub Actions from bf2fb29. Full details are in CHANGELOG.md.
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:dCv4gYwb:k7O8l4Re"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dCv4gYwb:k7O8l4Re"
}

