Cold Sweat

2.3.7
* (1.20 - 1.21) Added compat for "Oh the Biomes We've Gone"
      - Tweaked the temperatures for 39 biomes from the mod
      - Chameleons now spawn in appropriate biomes from the mod
      ! world_settings.toml will need to be reset for these new temperature to apply
* Added (partial) compat for Vaklyrien Skies
      - Temperature emitted from blocks placed on a ship will now properly affect the player
      - More compatibility will be added in future updates
- (1.16) Goats now drop 1-2 mutton when killed

Fixes:
* Fixed crash on servers when rendering particles in some cases
- Fixed crash when updating configs from pre-2.3 versions if "Block Temperatures" is configured in a particular way
- Fixed the icebox's opening animation not synchronizing to all players on a server
- Fixed some particles not spawning for all players on a server when they should
* (1.16) Fixed custom mob spawning not working
- (1.18) Fixed chameleons spawning on invalid blocks
- (1.21) Fixed damage from freezing/overheating dealing knockback

Technical Changes:
* Implemented a new rendering manager (PostProcessShaderManager) to handle Cold Sweat's shaders
      - Circumvents Minecraft's normal post-processing shader system to improve compat and allow for stacking of shader effects
* Removed deprecated methods from the Temperature and GatherDefaultTempModifiersEvent classes
* Java-based BlockTemps' min/max effect, min/max temp, range, and fade are now fields instead of just method return values
      - These fields are now part of the constructor
      - The existing methods will return the values of these fields by default, but can still be overridden with no additional changes necessary
      - The old BlockTemp(Block... blocks) constructor is still present, and will initialize all other fields to a default value
* BlockTemp fading over distance is now handled outside the getTemperature() method, in BlockTempModifier
      - This means you will no longer need to calculate the fade yourself and can simply return the temperature of the block
      ! For BlockTemps that still calculate the fade in the old way, the new fade will still be applied on top of the old one
            - This isn't too bad, but it means the block will weaken exponentially