Progress counts only when the wetness of the player performing the action is
within the specified bounds at that instant. Bounds are the percent the
vitals HUD shows, 0 to 100.
Bounds are the HUD percent, not the game’s internal 0 to 1 fraction.
minWetness: 50 matches a player whose HUD reads 50% wet or more. This decision is by design to make it easier for you to author contracts based on what you would actually see in-game.
“While wet” is minWetness: 5, low enough to catch rain but not a stale
splash. Swimming pushes wetness far higher, so “while swimming” flavor
works with minWetness: 80.
Being wet drags core temperature down, so this pairs naturally with
Player Temperature for
freezing-swimmer contracts.
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 minWetness is greater than maxWetness, the plugin swaps them and
logs a warning.