Player Temperature
⭐ Premium
Progress counts only when the core temperature of the player performing the action is within the specified bounds at that instant. This is the temperature number on the vitals HUD, in degrees Celsius, so players can check their own screen against the contract’s requirement.
{ "type": "PlayerTemperature", "maxTemperature": 5}Fields
Section titled “Fields”| Field | Type | Description |
|---|---|---|
type | string | Exactly 'PlayerTemperature' |
minTemperature | number | null | Minimum core temperature in degrees Celsius, any sign. Null (or omitted) means no lower bound. |
maxTemperature | number | null | Maximum core temperature in degrees Celsius, any sign. Null (or omitted) means no upper bound. |
Warning thresholds
Section titled “Warning thresholds”The game’s own HUD warnings sit at fixed temperatures, which makes good anchors for bounds:
- Cold warning shows below
5. - Freezing damage starts below
1, and gets worse below-10and-20. - Hot warning shows above
40. Hydration also starts draining there. - Overheating damage starts above
60.
So “while cold” is maxTemperature: 5, “while freezing” is
maxTemperature: 1, and “while too hot” is minTemperature: 40.
- Bounds accept any sign. Deep cold biomes and swimming push temperature well below zero.
- Either bound can be
null(or omitted entirely) for “no limit on that side”, but at least one bound is required. A condition with neither bound would always be satisfied, so it is invalid and the contract will not load. - If
minTemperatureis greater thanmaxTemperature, the plugin swaps them and logs a warning. - Being wet drags core temperature down hard. A cold biome plus a swim is the fastest way to freeze, which pairs well with a Biome condition for arctic-themed contracts.
Examples
Section titled “Examples”Kill 3 players while freezing:
{ "type": "Kill", "amountRequired": 3, "entities": ["player"], "conditions": { "freezing": { "type": "PlayerTemperature", "maxTemperature": 1 } }}