Villager API Mod FAQ

Create a folder called `villagers` in your world's `datapacks` directory, then organize your JSON files inside it by profession name. The mod will automatically scan this folder when the world loads.

Yes—set up one profession file, then use the biome-specific trade system to assign different trade lists to the same job depending on where the villager spawns. This lets you create region-specific merchants without duplicating professions.

You can use any solid block in the game as a workstation—the mod doesn't restrict you to vanilla job blocks. Just reference the block's ID in your profession file.

In your trade list, use the item NBT syntax to specify enchantments, potion effects, or custom names directly in the trade entry. The mod will handle applying these properties when the trade occurs.

Yes, as long as all players have the mod installed and the datapack is placed in the server world folder or synced to clients. The mod handles synchronization automatically.

The mod doesn't have built-in player-specific trade restrictions, but you can work around this by using command blocks or other mods to control villager behavior based on player conditions.

The villager will spawn but won't link to a workstation, and they may not behave as expected. Always verify that your workstation block ID is spelled correctly and exists in your game version.

Custom villagers support the full range from novice to master, just like vanilla villagers. You define the trades for each level separately in your configuration file.

Yes—you can link treasure maps to vanilla Minecraft structures or custom structures added by other mods, and the maps will generate valid coordinates when the trade completes.

The mod is optimized for performance, but spawning hundreds of any mob type will impact your server or client; use reasonable numbers and consider spreading villagers across multiple locations.