Pick up and relocate supported objects
Move compatible blocks or mobs to a new position instead of rebuilding the same setup from scratch.
Compact Download Hub · S12
Carry On mod for a simpler Minecraft moving workflow
Review what Carry On does, compare loader compatibility, follow a clean installation checklist and reach the supplied download without unnecessary detours.
Platform
Minecraft Java
Loaders
Forge · Fabric · NeoForge
Focus
Carry compatible objects
Guide
Setup · Safety · Fixes
About / What Is
A utility mod built around moving compatible blocks and mobs
Carry On is known for letting players pick up supported tile entities and mobs and move them around. The practical value is reducing repetitive break-and-rebuild steps when reorganizing bases, farms or work areas.
✓
Short-distance utility
Useful when rearranging a build without treating every object as disposable.
Useful when rearranging a build without treating every object as disposable.
✓
Modded-instance friendly
Choose the file that matches the exact Minecraft version and loader.
Choose the file that matches the exact Minecraft version and loader.
Features
Core benefits in a compact feature band
The S12 layout keeps high-value information visible without turning every feature into a large repeated card grid.
Base organization
Reposition selected utility objects while refining rooms, farms and storage areas.
Loader choices
Use a release built for Forge, Fabric or NeoForge where available.
Version discipline
Match Minecraft, loader and mod release to reduce startup errors.
Config-aware use
Behavior can vary by object type, modpack rules and server configuration.
How It Works
Four-step usage and setup flow
The exact in-game controls can depend on version and configuration, so verify the controls shown by your installed release.
01 · CHECK
Match versions
Confirm Minecraft, loader and Carry On build before installation.
02 · INSTALL
Add the mod
Place the correct mod file into the active instance's mods folder.
03 · TEST
Use a safe world
Verify startup and behavior before using it on an important save.
04 · CARRY
Move supported items
Use the release's configured carry interaction on compatible targets.
Compatibility
Choose the right environment first
Carry On publishes loader-specific files. A mismatch is one of the fastest ways to create launch or loading problems.
Supported family
Forge
Use a Forge build that targets the same Minecraft version as your instance.
Supported family
Fabric
Do not mix a Fabric mod file into a Forge or NeoForge instance.
Supported family
NeoForge
Recent releases include NeoForge variants for supported game versions.
Use Cases
Where carrying can save repetitive work
Base redesign
Shift compatible utility blocks when changing a room layout.
Farm cleanup
Reposition supported entities or blocks during small farm changes.
Workshop moves
Keep a compact workshop flexible while expanding a build.
Testing layouts
Experiment with object placement in a backup or test world first.
Installation / Setup
Install with version matching, not guesswork
Use the mod loader and file built for your exact Minecraft version. Keep important worlds backed up before changing a modded instance.
1
Install or open the intended Forge, Fabric or NeoForge instance.
2
Place the matching Carry On mod file in that instance's
mods
folder.
3
Launch the same profile and confirm the mod loads without errors.
Download
Download Carry On mod
The primary button below uses the supplied project download URL. Before downloading, verify that this source archive and branch are the version you actually intend to use.
Safety Notice
Protect your worlds before changing a modded setup
Back up important saves, avoid mixing loader families, and do not assume a file built for one Minecraft version will work on another. This site is an independent guide and is not affiliated with Mojang, Microsoft, Minecraft, CurseForge or the Carry On project.
Pros and Cons
Useful convenience with compatibility tradeoffs
Pros
- Reduces some break-and-rebuild work.
- Fits base organization and small relocation tasks.
- Available across multiple Java mod-loader ecosystems.
Cons
- Not every block, mob or modded object will be compatible.
- Wrong versions can cause loading or startup issues.
- Behavior may vary by server or modpack configuration.
Release Information
Version checkpoints before you download
Use these keyword-relevant versions as compatibility checkpoints, not interchangeable files.
| Game line | What to verify | Loader note |
|---|---|---|
| Minecraft 26.2 | Use a release explicitly marked for 26.2 | Forge / Fabric / NeoForge builds may differ |
| Minecraft 26.1.2 | Do not substitute a 26.2 file | Match the loader family |
| Minecraft 1.21.11 | Choose a 1.21.11-specific build | Check release label carefully |
| Minecraft 1.20.1 | Use the correct 1.20.1 variant | Forge setups must use the Forge file |
Troubleshooting
Start with the smallest reproducible setup
Game will not start
Check the crash log for a version mismatch, missing dependency or loader conflict.
Mod not detected
Confirm you used the active instance's mods folder and launched the correct loader profile.
Carry action unavailable
Check configuration, object compatibility, keybinds and server restrictions.
Guides Preview
Continue with focused setup guides
Static guides cover installation, loader differences, common errors, safety and version-specific search intent.
FAQ
Carry On mod questions
Exactly 20 focused questions across compatibility, setup and troubleshooting.
It adds a carrying interaction for supported blocks and mobs so players can relocate them without always breaking and rebuilding the setup.
The mainstream mod-loader releases referenced here are for Minecraft Java Edition. Bedrock uses a different add-on system and should not use Java mod files.
Carry On has releases for Forge. Your exact Minecraft version, loader version and mod file still need to match.
Carry On also has Fabric releases for supported Minecraft versions. Use the Fabric build only inside a Fabric-based instance.
Recent releases include NeoForge builds. Check the intended game version and loader before installing.
No. Treat game versions as compatibility boundaries unless the release notes explicitly say otherwise.
No. Java mods and Bedrock add-ons use different systems, so a Java mod file should not be installed into Bedrock or Minecraft PE.
For multiplayer, use the release guidance for your chosen version and server setup. Matching mod environments avoids many connection and behavior issues.
No mod can assume universal compatibility. Some blocks, entities or other mods may be restricted or behave differently.
It is best treated as a short-distance utility for compatible objects, not as a replacement for inventories, logistics mods or bulk transport.
Install the matching mod loader, place the correct Carry On file in the instance mods folder, then start the same Minecraft profile and verify it loads.
The most common checks are game-version mismatch, wrong loader build, missing dependencies, duplicate files or a conflict with another mod.
Confirm the file is in the active instance mods folder, the correct loader is actually launching, and the mod file targets that Minecraft version.
Yes. Back up important worlds before changing loaders, mod versions or large modpacks.
Normally a loader mod is placed in the mods folder as provided. Do not unpack a mod JAR unless its documentation specifically instructs you to.
Record your current Minecraft version, loader, mod version and important world backups. Then read the release notes for changes.
Removing mods can change world behavior. Make a backup first and test a copy of the world when possible.
Compatibility, configuration, object type, protections or another mod can affect what is allowed to be carried.
Use clear provenance and verify what you are downloading. This site links the supplied project download URL and recommends checking version and source details before use.
Test with the smallest possible mod set: correct loader, Carry On, required dependencies, and a backup test world. Add other mods back gradually.