Tags
Creators
Details
ALPHA-2.1-P4
Compatibility
Changes
Prerelease. The fourth pilot of 2.1, Realism: EXTENDED: EZvac can now be extended. The save format is the same as 2.0 (format 6), so it's a drop-in upgrade, and servers have nothing new to set up: nothing changes for players unless an addon is installed. It includes everything in Pilots 1, 2 and 3.
A public API for addons (API 1.0)
Other plugins can now build on EZvac's climate. Addons are ordinary Paper plugins that depend: [EZvac] and call EzvacApi.get(). They can read:
- the climate at any spot, or around any player: temperature, feels like, humidity, the outdoors, weather, season, and which system conditions it. These are the same numbers the HUD shows;
- the outdoor climate: air, natural water, humidity, dew point, and how much the season shifts it;
- thermostats and their systems, and dehumidifiers and humidifiers;
- the seasons, and whether the server shows °F or °C.
And listen to events:
| Event | When |
|---|---|
PlayerClimateUpdateEvent |
Every player's climate is read again, every half second by default |
ThermostatModeChangeEvent |
A system starts cooling or heating, or goes idle |
ThermostatTargetChangeEvent |
A target changes, from the menu or the command |
EquipmentStateChangeEvent |
Equipment starts or stops |
SeasonChangeEvent |
A world's season turns |
API 1.0 reads only, and EZvac builds events only while something listens, so servers without addons see no difference at all.
For developers: the API is on JitPack:
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
<dependency>
<groupId>com.github.EZvac-Plugin.EZvac</groupId>
<artifactId>ezvac-api</artifactId>
<version>ALPHA-2.1-P4</version>
<scope>provided</scope>
</dependency>
The guide, with a complete example addon, is The EZvac API.
Coming next
LiveExposure, the first EZvac addon: heat and cold that wear down survival players caught in the elements, built on this API.
See the changelog for details.
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:yUOgmYHB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dCv4gYwb:yUOgmYHB"
}

