Tags
Creators
Details
ALPHA-2.0-P4
Compatibility
Changes
Prerelease. The fourth pilot of the 2.0 realism update: remote sensors and sensor hubs. The save format is the same as the earlier pilots (format 6), so it's a drop-in upgrade. See the Pilot 1 notes for everything 2.0 adds.
Sensors
A sensor is a button that measures the spot it's on. The button decides what it measures:
| Button | Measures |
|---|---|
| Stone button | Temperature |
| Polished blackstone button | Humidity |
| Mangrove button | Temperature and humidity |
/hvac create sensor [label]
- Readings: a sensor reads exactly what a thermometer at that spot would. One outside follows the weather.
- Pressing a sensor shows its reading in chat. It never sends a redstone signal, even when an arrow hits a wooden one.
Sensor hubs
/hvac create sensor-hub [label]
A sign that shows up to nine sensors, three to a page:
Home 1/3
Kitchen 72F 45%
Cellar 58%
Garden 64.2F
- Click the hub to turn the page.
- Sneak-click it to switch auto-flip on or off. Auto-flip turns the page every 5 seconds and stays on after a restart.
- One sensor can appear on several hubs. A sensor in an unloaded chunk shows
--. /hvac infoon a hub lists every sensor with its reading.
Linking with the sensor tool
/hvac sensor-tool gives a purple, glinting link tool:
- Click a sensor hub.
- Click sensors to link them.
- Sneak-click a sensor to unlink it.
Breaking a sensor, or the block it hangs on, takes it off every hub.
Changed
- The duct tool is now
/hvac duct-tool, next to the new/hvac sensor-tool./hvac toolstill works, and duct tools you already have keep working.
Verified
- 189 automated tests.
- Live, on Purpur 1.21.1:
- Sensors: all three button types were detected as the right kind.
- Hub: linking, paging and auto-flip worked, and auto-flip kept going after a restart.
- Pressing: a pressed sensor showed its reading while a lamp under it stayed off. An arrow on the wooden sensor powered nothing.
- Removal: a broken sensor came off its hub.
- In-game: tried before release.
Upgrading
Stop the server, replace the EZvac jar with EzVac-ALPHA-2.0-P4.jar, and start it again. Nothing needs converting.
The jar below was built by GitHub Actions from 66ba0a4. 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:cFxZsCtT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dCv4gYwb:cFxZsCtT"
}

