🦙 What it is
This is a Bedrock Edition add-on, not a Java mod. There is no extra program to install: you open one file, the game imports it, and it works on phones, tablets, consoles and Windows. The wandering trader is the most-murdered character in Minecraft, and this makes him notice. Every time one dies by somebody's hand, the next one shows up with a bigger escort of llamas, up to eleven. From the second escalation onward, if the trader catches fire the whole caravan turns on the nearest player, which is usually whoever is holding the flint and steel.
The first one is free, because nobody thinks of it as a killing. He wanders into your base, he will not stop drinking invisibility potions, and you deal with it. Then chat says your name and a number, and the number is only two, so who cares. Four traders later a train of llamas comes over the hill behind a man you now genuinely dread, and the moment you nudge him toward the lava you built for exactly this the entire escort turns around and looks at you. Somebody else's kill did that. You have never touched a trader in your life and the guild has your address.
👥 Playing with friends
One counter for the whole world, so one person's kills escalate traders for everybody
⚠️ Before you install
- Never been run in a client. Whether the caravan actually retaliates is unproven.
- It replaces the vanilla trader llama file wholesale, so it conflicts with any other add-on that touches trader llamas.
- One counter for the whole world means a friend's kills raise your tier. That is intended, not a bug.
- The tier only ever goes up during normal play. The only way back down is the playtest command /scriptevent hazardpay:settier.
⏱️ Your first 5 minutes
New to this mod? Do these in order and you will have seen the point of it.
- Open dist/hazard-pay.mcaddon. There is only one pack inside it.
- In your world's settings, turn on Hazard Pay under Behavior Packs. There is no resource pack to enable.
- Play normally. Tier 1 is identical to vanilla, so nothing will look different yet.
- Kill a wandering trader any way you like except letting a mob do it. Watch chat name you.
- Wait for the next trader and count the llamas: it is always the tier plus one.
- From tier 2 on, set him on fire while standing nearby, and then run.
🔁 How it works
It installs itself, and it is behaviour only
Bedrock add-ons are not Java mods. Opening dist/hazard-pay.mcaddon hands the pack to the game and you tick it on under Behavior Packs. There is no resource pack, no textures and no art in this build. Every escalation is behaviour. It needs no experimental features, but it does need Minecraft 1.26.30 or newer, which is higher than the other two ports and is entirely down to the entity override described below.
Tip: On a dedicated server, drop dist/loose/hazardpay_bp into behavior_packs and list it in world_behavior_packs.json.
The ladder is one line of arithmetic
Llamas equal the tier plus one. Tier 1 is two llamas, which is exactly vanilla, so the add-on is invisible until somebody actually kills a trader. Tier 2 is three llamas and turns on retaliation. Tier 3 is four and adds resistances. Tiers 4 through 9 are five through ten llamas. Tier 10 is the boss tier and is not built in this version.
Tip: Type /scriptevent hazardpay:status to see the current tier, the escort size and the last five incidents.
What counts as a kill
Any death of a wandering trader that a mob did not inflict. Direct damage, lava, fire, flint and steel, a fall, suffocation, drowning, cactus, a trap somebody set an hour earlier: all of it counts. Killed by a zombie is free, and that exclusion is what keeps the ladder meaningful; without it the tiers would climb overnight while you sleep. Despawning is not death and never registers. Every kill announces itself in chat, naming the person who owes.
Tip: An arrow counts as yours. Bedrock reports the shooter, not the arrow, as the attacker.
The burning rule
From tier 2, the moment the trader catches fire the caravan turns on the nearest player within 32 blocks. It fires on the instant of ignition rather than every tick while he burns, and it will not re-trigger for another two seconds. Lava and flint and steel leave nobody for vanilla to retaliate against, and that is exactly the gap this closes, and it is also the half of the mechanic players actually use.
Tip: It can and will blame a bystander who merely walked past a lava lake. That is deliberate.
Two leashes and a train
Exactly two llamas are leashed to the trader no matter the tier; every other llama joins the caravan chain behind them. That is the whole answer to what ten llamas look like without becoming a rendering mess. At tier 9 the escort assembles itself into a train snaking over a hill rather than a blob orbiting a man. The code counts what is actually leashed rather than assuming the game already did it, because a hand-summoned trader arrives with nothing attached at all.
Resistances from tier 3
Bedrock's scripting exposes no attributes, so the Java version's armour modifiers become hidden potion effects: Resistance and Health Boost from tier 3, both stronger from tier 7, with the particle swirls switched off so he does not sparkle like somebody who just drank something. Fire Resistance is pointedly not on the list, because burning is the interesting failure case and the entire point of the retaliation rule.
One counter for the whole world
The guild's memory is per world, not per player. One person's three kills put everybody on tier 4, and that is the intended social outcome: it makes trader deaths a group problem and generates the argument. The kill count is stored in its own slot rather than inside the incident log, so a corrupted log cannot reset everyone back to tier 1. The last twenty incidents are kept, each with the day, the cause and the name.
What the Bedrock version does not do
The guild guard from tier 4 (a reskinned pillager riding a leashed llama, passive until provoked) is not here, because it needs a custom entity, a resource pack and art. Nor are the per-tier trader textures, for the same reason: you cannot retexture one instance of a vanilla mob. The tier-10 boss is wired but nothing ever triggers it. There are no achievements, since Bedrock has no custom advancements. Knockback resistance is dropped outright because no potion effect matches it. And the retaliation targets the nearest player rather than a named one, so the Java version's 60-second memory of who set the trap and stepped back is gone.
🎒 Items & blocks
🦙
Wandering Trader
The vanilla mob, unchanged in appearance at every tier; no textures ship with this build. From tier 3 he carries hidden Resistance and Health Boost, and from tier 2 setting him alight is a mistake.
Where: He arrives on his own, as always. Or /scriptevent hazardpay:summon spawns one with a full escort where you are standing.
🦙
Trader Llama
Two are leashed to the trader and the rest ride the chain behind them. From tier 2, every llama within 32 blocks can be enraged at once, leashed or not, which closes vanilla's odd asymmetry where eight llamas calmly watch you stab their employer.
Where: Spawned automatically alongside the trader, one more per tier.
📜 Lore
Flavour, not rules. None of this changes how the mod behaves.
The guild
Nobody ever meets the guild. There is no office, no representative and no negotiation, only a line in chat, in gold, stating what happened and what the rate is now. The escort grows because the job got more dangerous, and the job got more dangerous because of you, and the paperwork appears to be entirely automatic.
Hazard pay
The title is the whole argument. A man walks between worlds carrying goods, and people kill him for a lead and two llamas. If the death rate goes up, the escort goes up. It is an entirely reasonable response, and it ends with eleven llamas spitting at a person who was just passing through.
🎁 Jokes & trivia
Bits you might miss
- Tier 1 is byte-for-byte vanilla. The add-on's opening move is that nothing happens.
- The entire escalation table, all ten rows of it, is the sum tier plus one.
- Being killed by a zombie is free. The guild only bills for deaths that were somebody's idea.
- The trader is deliberately never given Fire Resistance, on the grounds that making him fireproof would delete the best mechanic in the mod.
- Vanilla trader llamas will only ever choose to attack untamed wolves, which means an ordinarily angered llama is furious at nobody in particular.
- The bill arrives in gold text the instant the body hits the ground, with your name in it.
- Walk past a lava lake at the wrong moment at tier 9 and ten llamas conclude it was you.
From the workshop
- Bedrock's scripting has no way to tell a mob who to attack. The fix was to ship Mojang's entire trader llama definition (23 KB, 923 lines) plus one extra component group that targets the player family within 32 blocks.
- The price of that fix: overriding a vanilla mob replaces it wholesale, so the pack carries Mojang's 1.26.30 file and is version-locked to it. When Bedrock changes trader llamas, the merge has to be redone against a fresh copy.
- The obvious script workaround, hitting a llama for zero damage while pretending to be the player, was rejected because a zero-damage hit registering is unverified, and it would have failed silently.
- The escort code measures the llamas already present instead of assuming vanilla added two. The Java version hardcoded "minus two", which the port notes call the bug encoded as an API: a hand-summoned trader arrived with none and the whole escort came out short.
- A Java bug disappeared by construction in the port: there, an untouched trader read as attacked because two timestamps were both zero. Bedrock hands the hurt event over directly, so the state machine that caused it is gone.
- The calm event was extended to also clear the enraged group, so a fight with a wolf cannot leave the caravan permanently hostile.
❓ FAQ
Do I need Forge, NeoForge or a mod loader?
No. Those are Java Edition things. This is a Bedrock add-on: open the file, the game imports it, tick it on in your world's settings.
Where is the resource pack?
There isn't one. This build is behaviour only: no textures, no models, no art. Everything that escalates is something the traders and llamas do, not something they look like.
Why does this need 1.26.30 when the other Bedrock ports need 1.21.80?
Because it replaces the vanilla trader llama's definition to make the caravan able to target players, and that means shipping the version of the file it was merged against.
Will it work alongside other add-ons?
Not alongside anything else that changes trader llamas. Whichever pack loads last wins, and this one replaces the whole file.
I installed it and nothing is different.
That is correct. Tier 1 is vanilla. Kill a trader yourself and the ladder starts.
Has anybody actually played this?
No. It builds, it validates and 16 offline tests pass, but it has never been run inside the game. The single biggest unknown is whether the retaliation fires at all.
⬇️ Get it
Status: The jar compiles and the author has tested it himself, but it has not had a real playtest yet.
- Install Bedrock for Minecraft 1.26.30+. The
install guide walks through this assuming no prior knowledge.
- Drop the mod's
.jar file into your mods folder.
- The server only (players join normally).
- Launch the game with that loader's profile selected.
📦 Where is the file?
This wiki documents the mods; it does
not host them. Builds live in the project's own repository under
be-hazard-pay/build/libs/.
Add-on by Bulletpies. Bedrock port of the NeoForge original, mc-hazard-pay.
↑ Back to top · ← All mods
