Shifting-Wares: VillagerConfig Addon

This addon provides compatibility between ShiftingWares and VillagerConfig modifications, allowing the ShiftingWares trade refresh system to use custom trades and layouts defined through VillagerConfig.

Compatibility with Shifting Wares Versions

Shifting Wares v2

For proper map caching functionality in Shifting Wares, exploration map trades must use the same item naming system as standard Minecraft trading. Otherwise, behavior may be unpredictable.

Shifting Wares v3

With this addon, map persistence can be defined directly in trade settings along with costs and results:

• shiftingwares:isPersistent: (boolean) Forcibly marks the trade as persistent. The refreshability of such a trade will be limited to the same conditions as map trading.

• shiftingwares:tradeId: (identifier) Allows ShiftingWares to associate an existing trade with its source in the datapack and prevent duplication of that trade.

Usage Example

{
    "shiftingwares:isPersistent": true,
    "shiftingwares:tradeId": "minecraft:on_ocean_explorer_maps",
    "cost_a": { "type": "minecraft:item", "name": "minecraft:emerald" },
    "cost_b": { "type": "minecraft:item", "name": "minecraft:compass" },
    "result": {
        "type": "minecraft:item",
        "name": "minecraft:map",
        "functions": [
            {
                "decoration": "minecraft:monument",
                "destination": "minecraft:on_ocean_explorer_maps",
                "function": "minecraft:exploration_map",
                "search_radius": 100
            }
        ],
    }
}

This data will not be present by default when VillagerConfig generates data from standard trading, but map trades will still be marked as persistent even without it. Setting the trade identifier is recommended to avoid duplication.

The trade identifier does not necessarily have to match the map's destination; this example simply shows how ShiftingWares handles them without VillagerConfig.

Version Support