- check_circle Functions
- 12,489 views, 1 today
- 713 downloads, 0 today
11
This datapack will count the villagers and iron golems that are in a village if the player rings a bell there.

The datapack will highlight often used villager professions like the librarians and the farmers and will gray out types that cannot be traded with.
It will also count baby villagers seperately.
UPDATE
Since version 2, players will be able to change their settings on how long the scoreboard will be displayed for them by using
WARNING: If you use teams yourself or in any other datapack, version 2 WILL BREAK them, use this version instead! If you need to switch from version 2, run
INSTALLATION
Download the .zip-file of the desired datapack and save it in
The world folder can be found by selecting the world (not starting it) and clicking on the "Edit" button on the bottom left corner. There simply choose "Open world folder" to open the folder and paste the datapack into the "datapacks" folder. (Create the folder if there is none.) The datapack should now be enabled when the world gets started.
If this is not the case: If cheats are enabled in the Minecraft world, type
DEINSTALLATION
To remove the datapack completely, run
Check out my other datapacks!
A list of my datapacks can be found at my GitHub page: https://github.com/manuel-st/mc-datapacks/

The datapack will highlight often used villager professions like the librarians and the farmers and will gray out types that cannot be traded with.
It will also count baby villagers seperately.
UPDATE
Since version 2, players will be able to change their settings on how long the scoreboard will be displayed for them by using
/trigger vc_settings
in the chat box. Additionally, players that didn't rung a bell or chose to hide the scoreboard will no longer see it when any other player rings a bell.WARNING: If you use teams yourself or in any other datapack, version 2 WILL BREAK them, use this version instead! If you need to switch from version 2, run
/function villager_counter:uninstall
first.INSTALLATION
Download the .zip-file of the desired datapack and save it in
.minecraft/saves/*your-worldname*/datapacks/
without unzipping it. *your-worldname* is the folder of the Minecraft world the pack should be installed in.The world folder can be found by selecting the world (not starting it) and clicking on the "Edit" button on the bottom left corner. There simply choose "Open world folder" to open the folder and paste the datapack into the "datapacks" folder. (Create the folder if there is none.) The datapack should now be enabled when the world gets started.
If this is not the case: If cheats are enabled in the Minecraft world, type
/datapack list enabled
into the chat box and press ENTER. It should now display a message that contains [file/*name-of-the-pack*.zip] .
Otherwise use /reload
DEINSTALLATION
To remove the datapack completely, run
/function villager_counter:uninstall
before removing it from the datapacks folder.Check out my other datapacks!
A list of my datapacks can be found at my GitHub page: https://github.com/manuel-st/mc-datapacks/
Compatibility | Minecraft 1.14 |
Tags |
2 Update Logs
Update #2 : by manuelst 11/16/2019 11:47:56 amNov 16th, 2019
Added a datapack with the fixes from v2 that is compatible with teams. Use only if you cannot use version 2!
LOAD MORE LOGS
4397739
119
Create an account or sign in to comment.
https://github.com/manuel-st/mc-datapacks/blob/master/_packs/Villager_Counter-V3.zip
To switch from version 2 to this version, run "/function villager_counter:uninstall" first, then remove the datapack and add the new one. Lastly, run "/reload".
To set it globally, you can run
/scoreboard players set @a vc_hideboard 400
The 400 is the time in ticks the scoreboards will stay up. (400 ticks = 20 seconds. Change it to the value you like.) You can override the complete "settings.mcfunction" file with this line. Players won't be able to change their value any more and will always get this time.There is a bug that you sometimes have to re-ring the bell after you changed it for changes to take effect and I didn't figure out how to solve it yet.
And to use scoreboards wouldn't cause any problems for the packs. It's creating teams that would break them.