iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
A lead is Minecraft’s item for moving an eligible mob with you or tethering it to an anchor. In current Java 1.21.6 and Bedrock 1.21.90, craft it from five string items—not the slimeball recipe shown in many older tutorials. Use the finished lead on a mob, then use it on a fence to create a leash knot; current Bedrock versions also support selected wall and entity connections.
This guide shows the current recipe, the exact leashing workflow, how to recover a lead, why a connection snaps, how multiple mobs share an anchor, and which Java and Bedrock mechanics are version-sensitive.
Free tools Windows power users keep installed
One-click scans. No signup required.
What a lead does in Minecraft
A lead creates a connection between you and an eligible mob, or between that mob and an anchor such as a fence. While you are holding the connection, the mob follows as you move. When you anchor it, the game displays a leash knot at the fence and keeps the mob near that post.
Leads are useful for moving animals into pens, positioning golems, arranging a group for transport, and keeping a selected mob near a building. They are not a universal control for every entity. The reference mechanics describe support for passive and neutral animals, golems, and some monsters, while hostile-mob support is not universal. Treat each mob as a compatibility question rather than assuming that every creature—or every villager—can be leashed.
#1 Best Overall
How to craft a lead in current Minecraft
Java 1.21.6 and Bedrock 1.21.90 document a recipe change: the slimeball ingredient was replaced by string. The current pattern uses five string items in a crafting table.
| Edition and release | Current ingredient pattern | What changed from older guides |
|---|---|---|
| Java Edition 1.21.6 | Five string items in the pattern below | Older four-string-and-one-slimeball instructions are outdated for this release. |
| Bedrock Edition 1.21.90 | Five string items in the pattern below | The same slimeball-to-string change applies in this release. |
The five-string crafting-grid pattern
Use a 3×3 crafting table and place string in these five cells:
| Top-left | Top-middle | Top-right |
|---|---|---|
| String | String | Empty |
| String | String | Empty |
| Empty | Empty | String |
The arrangement is a diagonal-hook shape: two strings across the top, two in the left and center positions of the middle area, and one at the bottom-right. The output slot should show leads. If it does not, first check that you opened a full crafting table rather than a smaller personal grid and that all five cells contain string.
Crafting steps
- Collect at least five string items.
- Open a crafting table so the 3×3 grid is available.
- Place the string exactly as shown: top-left, top-middle, middle-left, center, and bottom-right.
- Move the lead output into your inventory or hotbar.
- Repeat the pattern for additional leads when you need separate connections.
Why an old slimeball recipe fails
Many videos and screenshots were made before the current recipe update. They show four strings and one slimeball. In Java 1.21.6 and Bedrock 1.21.90, that ingredient is no longer the current recipe component. Replacing the slimeball with string is the first fix when an otherwise familiar pattern produces no result.
How to leash a mob to yourself
The hand-leashing process is short, but the order matters. You must select a compatible mob and have the lead in your active hotbar slot.
- Put a lead in your hotbar and select it.
- Face the mob you want to move.
- Use the lead on that mob. A visible line indicates that the mob is attached to you.
- Walk while keeping the mob within the connection’s allowed distance.
Controls differ by platform, so use the normal interact or use button for your edition. If the mob does not attach, the most likely explanation is eligibility rather than a missing combat or movement input: leads do not work on every entity.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Moving a leashed mob safely
Walk rather than sprinting away from the mob when you are learning the mechanic. Watch the line as terrain, corners, and elevation change. A fence, wall, or other obstruction can make a route awkward even when the mob itself is supported. If the line disappears, stop and check whether the mob is still attached before continuing.
How to leash a mob to a fence
Fence tethering turns a temporary hand connection into an anchored one.
- Use a lead on an eligible mob so the mob is attached to you.
- Walk to the fencepost where you want the mob to stay.
- With the lead still selected, use it on the fence.
- Look for the visible leash knot on the fencepost. The mob is now anchored there instead of following your hand.
Minecraft’s official Taking Inventory: Lead article describes the behavior this way: “While holding a mob on a lead, you can hit the ‘use’ button on any kind of fence to tie the mob to that fence, keeping it within five blocks of the fencepost.” The five-block figure is the fence-tether behavior; it is not the same measurement as the distance at which a lead connection snaps.
Using a wall as an anchor
Supported Bedrock releases document leash connections involving walls. If a Bedrock wall accepts the use action, treat it as the equivalent of a fence anchor and look for the leash knot. Do not assume that an identical wall interaction exists in every Java release; edition and version determine which anchor blocks are supported.
Rank #3
Anchoring more than one mob
Multiple leads can share one fencepost. Attach each compatible mob to yourself, bring it to the same post, and use the lead on that post. Each connection is represented at the anchor, allowing a small group to remain associated with one fence rather than requiring a separate post for every mob.
For a tidy pen, place the post where the five-block tether area overlaps the space you want the animals to occupy. A post at the edge of a narrow enclosure gives less useful room than one near its center. If mobs crowd one another, separate posts reduce tangling and make individual release easier.
How to get a lead back
To release a mob, use the lead interaction on the mob again or interact with the leash knot. Removing the fence can also detach a fence-anchored connection. In normal play, these release actions are the way to recover the lead for another use: look for the item after the connection is removed and pick it up if it lands on the ground.
Newer mechanics also document shears as a way to remove leash connections. Because shears-based removal is edition- and version-sensitive, try the documented interaction for the release you are running rather than relying on an older control guide.
Releasing one mob from a shared post
When several mobs use one fencepost, target the specific mob or its individual leash connection. Removing the fence itself can affect every connection anchored there, so use the mob or knot interaction when you want a single release. If your edition exposes several leash knots in the same area, move your view until the intended connection highlights before interacting.
Rank #4
Why did my lead break?
A lead connection can snap when its distance limit is exceeded. Mojang’s Java 1.21.6 notes and Bedrock 1.21.90 notes describe a standard 12-block snapping distance. They also describe a 16-block exception for a happy ghast. These values are tied to those releases and should not be treated as timeless behavior for every historical or future version.
Common distance-related causes
- You walked too far from a hand-leashed mob.
- The mob moved around terrain and the stretched connection exceeded the limit.
- An anchored mob wandered far enough from its post to reach the snapping threshold.
- A happy ghast was involved, in which case the documented exception is 16 blocks rather than the standard 12.
The five-block fence range and the 12-block snapping distance answer different questions. Five blocks describes where a fence-tied mob is kept relative to its fencepost in the official article. Twelve blocks describes when a current-version connection can snap. Keeping those figures separate prevents a common troubleshooting mistake.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What to do after a snap
- Return to the fence, knot, or last position where you saw the mob.
- Check the ground for the detached lead and pick it up.
- Confirm that the mob is still present and eligible.
- Reconnect it and shorten the route if distance caused the failure.
- For a group, anchor mobs one at a time so you can identify which connection fails.
Which mobs can use a lead?
Lead support covers passive and neutral animals, golems, and some monsters according to the reference mechanics. The important qualification is “some”: hostile-mob eligibility is not universal. A mob’s presence in the world does not guarantee that the use action will attach a lead.
- Test one specimen before building a transport route around it.
- Do not promise that every villager or every hostile mob can be tethered.
- If the use action has no effect, verify the mob’s support in the mechanics for your edition and release.
- Do not diagnose a failed attachment as a recipe problem when the lead is already visible in your hand.
This compatibility limit matters for farms and displays. Design the enclosure around entities that are confirmed to accept leads, and keep an alternate plan for entities that must be moved by another method.
Java and Bedrock: current leash differences
The core workflow is shared, but recent releases add different details. The following comparison is limited to the current versions documented for this guide.
| Mechanic | Java Edition 1.21.6 | Bedrock Edition 1.21.90 |
|---|---|---|
| Lead recipe | Five-string pattern; the older slimeball ingredient is replaced. | Five-string pattern; the older slimeball ingredient is replaced. |
| Fence attachment | Use a leashed mob on a fence to create a leash knot. | Use a leashed mob on a fence to create a leash knot. |
| Wall attachment | Do not assume wall support from the Bedrock behavior. | Supported wall interactions are documented for current mechanics. |
| Entity-to-entity attachment | Newer release notes describe sneak-interacting with another mob to attach already-leashed mobs. | Version 1.21.90 documents entity-to-entity leashing. |
| Shears | Newer mechanics document shears for removing leash connections. | Version 1.21.90 documents shears-based removal. |
| Documented snapping distance | 12 blocks normally; 16 blocks for a happy ghast. | 12 blocks normally; 16 blocks for a happy ghast. |
If a tutorial gives a different recipe, control, or attachment target, compare its edition and release with the table before assuming your game is malfunctioning.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Advanced current-version feature: chaining mobs
Recent Java notes describe a way to attach already-leashed mobs to another mob by sneak-interacting with it. Bedrock 1.21.90 documents entity-to-entity leashing as well. This allows a chain rather than forcing every mob to connect directly to a fencepost or to the player.
A cautious chaining procedure
- Leash the first mob normally.
- Leash the second mob or place it where the game can target it.
- Use the sneak modifier while interacting with the target mob, following your edition’s current control mapping.
- Look for the new visible connection before moving the group.
- Test the chain over a short distance before taking it through a crowded area.
Chaining is a current-version feature, not a guarantee for every older world or every entity type. If the sneak interaction does nothing, confirm the release, target eligibility, and whether both mobs already have supported leash connections.
Removing a chained connection
Use the documented shears interaction where available, or interact with the relevant mob or leash knot. Avoid breaking a shared fence when you only want to remove one link, because an anchor change can affect more than the connection you intended to edit.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Hand-leashing versus fence tethering
Choose the method based on how long the mob must remain in place.
Recommended Free Tools
| Method | Movement | Best use | Main risk |
|---|---|---|---|
| Lead held by the player | The mob follows as you travel. | Short transports and repositioning. | The connection can snap if distance reaches the current limit. |
| Fence or supported wall | The mob remains near its anchor, within the official five-block fence range. | Temporary pens, staging areas, and displays. | Removing the anchor can detach its connections. |
| Entity-to-entity chain | One connection can link to another mob. | Current-version group movement experiments. | Support and controls vary by edition and release. |
For a permanent-looking enclosure, a fence anchor is easier to inspect than a mob-to-mob chain. For a one-time move, holding the lead avoids leaving a knot behind. For a group, a shared post is simpler to troubleshoot than a long chain when you need individual control.
Troubleshooting checklist
The crafting table shows no lead output
- Confirm that you are using a 3×3 crafting table.
- Replace any slimeball with string if you are on Java 1.21.6 or Bedrock 1.21.90.
- Count five strings and verify the top-left, top-middle, middle-left, center, and bottom-right cells.
- Check the edition and exact release; older versions may follow different recipe rules.
The mob will not attach
- Make sure the lead is selected in the hotbar.
- Use the normal interact button on the mob rather than attacking it.
- Try a known passive or neutral animal or a golem to separate a control problem from an eligibility problem.
- Do not assume that a villager or hostile mob is supported.
The fence does not create a knot
- Attach the mob to yourself first; an unattached mob cannot be transferred to a fence through the normal sequence.
- Use the lead on the fencepost while the lead is still selected.
- Try a fence rather than a wall if you are on Java.
- On Bedrock, verify that your release supports the wall interaction you are attempting.
The mob escaped after I left it tied
- Check whether the fence or wall was removed.
- Check the mob’s distance from the anchor and the current 12-block snapping rule.
- Remember that the official five-block fence range is a position guideline, not permission to stretch the lead indefinitely.
- Reconnect the mob closer to the post and observe it before leaving the area.
I cannot find the lead after releasing a mob
- Inspect the ground around the mob and the leash knot.
- Check whether you released the intended connection or removed an anchor affecting several mobs.
- Search the route if the connection snapped while the mob was moving.
- Craft a replacement only after checking the release location; a detached item can be easy to miss in grass or around fences.
A reliable setup for pens and transport
Building a small holding pen
- Place a fencepost where you want the leash knot.
- Leave enough open space for the official five-block tether area to overlap the pen.
- Bring one confirmed-compatible mob to the post.
- Anchor it and watch its movement before adding more.
- Use the same post for additional mobs only if the resulting crowding is acceptable.
Moving a group
- Prepare the destination before attaching the first mob.
- Move mobs in small groups so a snapped connection does not leave the entire group untracked.
- Keep routes short and avoid sharp terrain changes that stretch the line.
- At the destination, anchor each mob to a fence or use the documented current-version chaining feature.
- Release individual mobs through their connections rather than dismantling a shared anchor unless you intend to detach all of them.
Version-proof checklist
- Identify Java or Bedrock and record the full release number.
- For Java 1.21.6 and Bedrock 1.21.90, use five strings in the current pattern.
- Keep the old four-string-and-slimeball recipe only as historical information, not as the current instruction.
- Use a fence for the cross-edition workflow; treat Bedrock wall support as version-specific.
- Expect a 12-block standard snapping distance in the documented current releases and 16 blocks for a happy ghast.
- Label entity chaining and shears removal as newer mechanics rather than universal behavior.
- Test mob eligibility before designing a farm, display, or transport route around a lead.
Bottom line
In Java 1.21.6 and Bedrock 1.21.90, craft a lead with five strings in the current 3×3 pattern. Use it on a supported mob, then use it on a fence to create a leash knot that keeps the mob within five blocks of the post. Recover a lead by releasing the mob or knot, watch the 12-block snapping limit, and verify edition-specific features such as walls, chaining, and shears before relying on them.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
