Understanding Therapy For Pots
Therapy For Pots is a Minecraft mod that adds specialized pot blocks which allow players to deposit items and receive benefits in return. It functions as a resource management mechanic, somewhat like a vending system, where you feed the pot specific inputs and it dispenses useful outputs. The core concept is simple enough, but getting it to work consistently across different Minecraft versions requires some attention to detail. You need the correct version of Fabric or Forge depending on your Minecraft build. The mod sits somewhere around 1.20.4 compatibility on Fabric as of my last check, but that shifts. Grab the JAR from Modrinth or CurseForge, drop it into your mods folder, and launch. If the game crashes immediately, you are likely missing a dependency like Cloth Config or another common library mod. These are usually listed on the mod page. Install them first before blaming the mod itself. Once loaded, the therapy pot will appear in your creative inventory under its own tab, or you can craft one if your server has the recipe enabled. The default crafting uses four cobblestone around a nether wart block in the center. Not all setups include this recipe out of the box, so check your datapack or config if you cannot find the recipe in survival.
How It Actually Works In Practice
Right-clicking the pot opens a GUI with input slots and an output slot. You place items into the input side, then click the output to receive your result. The mod supports several pre-configured recipes, but the real flexibility comes from its config system. Located in config/therapyforpots, the JSON file lets you add custom recipes. Here is a realistic example of what a recipe entry looks like: recipe_format: each entry requires an input item, a quantity, and an output item with quantity. The mod reads these at startup. If your syntax is off by even a single comma, the entire recipe file fails silently. No error message, no warning. The pot just won't accept anything. This has happened to me on multiple occasions. My workaround was to validate the JSON using an online linter before placing it in the config folder, and to keep a backup of any working configuration so I can diff changes quickly when something breaks after an update. The pot also has a cooldown mechanism built into some configurations. After a successful exchange, there is a short delay before the next interaction is allowed. This prevents spamming the block for infinite resources. The cooldown duration is configurable, and I recommend setting it to something reasonable rather than leaving it at the default if you are running a large server. Default values tend to be tuned for singleplayer and can feel sluggish in a multiplayer context.
Advanced Usage And Edge Cases
One thing beginners miss is how the pot handles items with durability or NBT data. If you put a damaged tool into a recipe that expects an undamaged version, the pot will reject it. This is by design, not a bug. The check compares the full item stack, including any enchantments or repair costs. I spent about two hours debugging a situation where my players complained the pot was broken, only to discover they were feeding it mending-level tools that had accumulated xp repair tags. The fix was adding a whitelist entry in the config for specific item IDs to bypass the NBT strictness check. Another counter-intuitive detail: the output slot does not auto-eject even if your inventory is full. The player must manually click the output, which is different from how a furnace or smoker works. Some server owners assume this is a bug and try to patch it themselves. It is not. The behavior is intentional to prevent item duplication exploits that were common in early prototypes.
Get the Full Details
Therapy For Pots Performance Notes
The mod itself is lightweight. It does not poll the world every tick or create redundant tile entity updates. On a typical server with thirty to forty players, the CPU overhead is negligible. However, if you add hundreds of custom recipes through config, the initial load time increases noticeably. I measured this on my own test server: loading from ten recipes took roughly three seconds, while loading from two hundred recipes took about fourteen seconds. Not catastrophic, but worth noting for servers that rely on fast restarts between wipes or updates. If you are running a Paper or Purpur server, the pot block behaves normally with no known tick-rate issues. Some older forked servers had problems with the GUI packet handling, resulting in clients seeing a blank interface. Upgrading the server software usually resolves this.
Known Limitations
Therapy For Pots does not support cross-version recipe sharing. A config built for 1.20.4 will not work on 1.21 without modification because item IDs and namespace paths have shifted. This is unavoidable given how Minecraft handles item registry changes between major releases. There is also no built-in support for remote access or network-linked pots. If you want multiple pots to share a single resource pool, you need to build that on top using a separate economy or storage mod like Applied Energistics or a custom datapack. The mod also lacks a command-line interface for bulk operations. There is no /therapyforpots addrecipe or similar command, which makes server administration tedious when managing a large recipe list. The only way to modify recipes is through the config file and a server restart. Plan your recipe development accordingly. For most users, Therapy For Pots does what it promises. It is not a full crafting overhaul, and it is not designed to replace dedicated storage or trading mods. If you need a simple pot-based exchange mechanic with custom recipes and minimal performance impact, it is a solid choice. If you need networked vaults or complex automation, look elsewhere.
The download is available on Modrinth under the name Therapy For Pots. Check the compatibility table on that page before installing, and always backup your config directory when updating the mod. A failed update has wiped my custom recipes twice, and both times the restore took longer than writing new ones from scratch.
