- check_circle Advancements
- check_circle Functions
- 12,246 views, 4 today
- 1,627 downloads, 1 today
30
NOTE: UPDATING
Before you update PLEASE make sure you use the command /scoreboard objectives remove traderTimer right before reloading. This scoreboard has changed across versions and must be cleared.
Does it ever seem like the Wandering Trader takes forever to spawn? This datapack fixes that!
The random spawn attempt mechanic used by vanilla Minecraft to spawn wandering traders is disabled, and a hard cooldown is instead placed on their spawning. Every 30 minutes of real time that a player is logged in, a trader and their llamas will be spawned randomly nearby. The cooldowns are individualized to every player, so that multiple players can have a wandering trader at once.
The despawn delays on traders are also lowered to 10 minutes, so that there are 20 minute gaps between wandering trader visits. However, the spawn delay can be changed in the advancements/traderspawn.json and the despawn delay can be changed in the functions/spawn.mcfunction files.
While wandering traders are not always incredibly useful, they can be invaluable in certain gamemodes, such as skyblock or single-biome survival. This datapack should help in these scenarios by lessening the waiting game associated with acquiring the materials locked behind wandering traders.
This should be compatible with any datapack that alters the wandering trader's trades. If you find one that isn't compatible, let me know in the comments!
Before you update PLEASE make sure you use the command /scoreboard objectives remove traderTimer right before reloading. This scoreboard has changed across versions and must be cleared.
Does it ever seem like the Wandering Trader takes forever to spawn? This datapack fixes that!
The random spawn attempt mechanic used by vanilla Minecraft to spawn wandering traders is disabled, and a hard cooldown is instead placed on their spawning. Every 30 minutes of real time that a player is logged in, a trader and their llamas will be spawned randomly nearby. The cooldowns are individualized to every player, so that multiple players can have a wandering trader at once.
The despawn delays on traders are also lowered to 10 minutes, so that there are 20 minute gaps between wandering trader visits. However, the spawn delay can be changed in the advancements/traderspawn.json and the despawn delay can be changed in the functions/spawn.mcfunction files.
While wandering traders are not always incredibly useful, they can be invaluable in certain gamemodes, such as skyblock or single-biome survival. This datapack should help in these scenarios by lessening the waiting game associated with acquiring the materials locked behind wandering traders.
This should be compatible with any datapack that alters the wandering trader's trades. If you find one that isn't compatible, let me know in the comments!
Credit | pizzaspren#3030 for HUGE Help |
Compatibility | Minecraft 1.17 |
to | Minecraft 1.18 |
Tags |
3 Update Logs
1.17-1.18 Update - Fixed : by terezridax 12/16/2021 4:16:00 pmDec 16th, 2021
Changed play_one_minute scoreboard to play_time.
Make sure to use /scoreboard objectives remove traderTimer to ensure the fix works.
This means the datapack will also not work pre-1.17 unless you change the scoreboard criteria in /data/tradercycle/load.mcfunction and clear the existing scoreboard.
Make sure to use /scoreboard objectives remove traderTimer to ensure the fix works.
This means the datapack will also not work pre-1.17 unless you change the scoreboard criteria in /data/tradercycle/load.mcfunction and clear the existing scoreboard.
LOAD MORE LOGS
tools/tracking
4741222
119
frequent-flyer-more-frequent-wandering-trader
Create an account or sign in to comment.
I have been playing for 4 hours and not even 1 has spawnedi have used the function command (tradercycle load and tradercycle spawn) just to see what it did and never got any traders again
Nevermind, I see in the same update note "Changed play_one_minute scoreboard to play_time."
Works great, thank you.
It's like it's a co-routine or something taking up all the commands so no other datapack have access to function.