MAmbience

Additional/Alternate downloads:

1. Vanilla clients connecting to a server have to use the resourcepack: Link

2. Servers can use the alternate "noAssets" file which does not include the resourcepack: Link

3. Sounds/Effects/... are defined in datapack files, see this download for the defaults as an example: Link

Changelog Version 5.0.0:

• Updated for MC 1.18.2
• Added config toggle for disabling wind sounds
• Added new system for sound triggers (currently available triggers: SECOND(default), TICK, ATTACK_SWING, ATTACK_BLOCK, ATTACK_HIT, USE_ITEM_MAINHAND, USE_ITEM_OFFHAND)
• Added preliminary support for Terralith 2
• Switch to using biome tags and other data definition refactors (see default data for new format)
  • Refactor condition system to make use of more extendable variable system (old conditions are still useable and get converted during load)
  • Added some sounds ("item equip" and "sword attack") using some of the new capabilities (advanced variable stuff is mostly unused for now - but available for custom sound packs)
  • Added ITEM_HELD, VARIABLE and VARIABLE_CHANGED condition (see below for more info)

Number Variables:
    Example: { "condition": "VARIABLE", "variable": "health", "minValue": 0, "maxValue": 2 }
    Available: x, y, z, health, foodLevel, time, temperature, humidity
Boolean Variables:
    Example: { "condition": "VARIABLE", "variable": "submerged" }
    Available: sneaking, jumping, onGround, exposed, underground, submerged, raining, thundering
String Variables: 
    NOTE: The only current String variables are less usefull than the HELD_ITEM condition, which supports item tag checks in addition to single items
    Example: { "condition": "VARIABLE", "variable": "itemMainHand", "stringValue": "minecraft:apple" }
    Available: itemMainHand, itemOffHand
The VARIABLE condition supports an additional boolean parameter "previous" which when true will use the value from the previous tick
    usefull for detecting transitions (for simple changes use VARIABLE_CHANGED) 
    BUT note that normal (trigger=SECOND) sounds might "skip changes" -> use the TICK trigger but be carefull of the performance impact when adding a large number of TICK triggered sounds
The VARIABLE_CHANGED condition will only return true if the variable has changed between the current and last tick

Example Definition File adding the "annoying low health beep":
{
    "sound": {
        "name": "minecraft:block.note_block.banjo",
        "volume": 100,
        "pitchMin": 200,
        "pitchMax": 200
    },
    "trigger": "SECOND",
    "conditions": [
        {
            "condition": "VARIABLE",
            "variable": "health",
            "minValue": 0,
            "maxValue": 2
        }
    ],
    "restrictions": [],
    "cooldownMin": 0,
    "cooldownMax": 0
}

Supported Versions:

• Fabric: 1.18.2