Terraria 1.4.5.0 does not introduce a separate placeable block officially called an item hopper. Instead, the update gives two existing mechanisms complementary jobs: a chest that receives a wire signal can collect nearby dropped items, while conveyor belts move items along a route and can now carry them upward. The chest is the collection point; the belt is the transport system. Because the update notes never define how far “nearby” reaches, any design promising a precise pickup radius would be guesswork.
The feature appears in the official 1.4.5.0 update notes, released for the “Bigger and Boulder” update on January 27, 2026. Your platform and exact build still matter when a setup behaves differently, especially on console.
What is an “item hopper” in Terraria 1.4.5?
In Terraria terminology, “item hopper” is a useful comparison rather than the name of a newly added block. The 1.4.5.0 notes describe a change under wiring and mechanisms: when a chest receives a wire signal, it picks up nearby dropped items. The chest itself performs the collection; there is no separate hopper object identified in those notes.
The update notes state: “When Chests receive a wire signal they now pick up all nearby dropped items. Great for automated farms!” That sentence establishes the trigger and the general result, but not a measured distance, a timer interval, a filtering rule, or one required circuit layout. Treat those omitted details as unknown rather than filling them in with a number from another game.
Collection and transport are different jobs
A wired chest is an area-collection tool. It waits for a wire signal and then gathers eligible dropped items that are nearby. A conveyor belt is a route tool. It moves items from one tile or section of a build toward another, with belt direction and the surrounding tiles influencing where an item ends up.
That distinction determines how to plan a farm. Put a chest where you want drops consolidated, and use belts to bring items toward that location or to move them onward after collection. A belt does not replace the signal-triggered chest behavior, and a chest does not create a moving route by itself.
How do I make a wired chest collect dropped items?
The reliable principle is simple: place a chest in the collection area and connect it to a circuit that sends a wire signal. When the signal reaches the chest, the 1.4.5.0 behavior allows it to pick up nearby dropped items. The notes do not require a particular switch, timer period, or wiring pattern, so select a trigger that fits your farm and platform.
- Choose the collection point. Place the chest where drops will accumulate or where a conveyor route can deliver them. Keep the intended drop zone close enough to the chest for the game’s undefined “nearby” condition; do not design around a claimed number of tiles.
- Connect the chest to a wire circuit. Run a wire from the chest to a trigger of your choice. The important requirement is that a signal reaches the chest, not that you copy a specific layout from another game.
- Activate the circuit. Send a wire signal while dropped items are present. A successful activation should cause the chest to collect nearby drops under the 1.4.5.0 rule.
- Observe the result before expanding the farm. Test the chest with drops at several positions in the intended collection area. This reveals the practical reach of your particular arrangement without pretending that the update notes publish a universal radius.
- Route overflow deliberately. If items land outside the tested collection area, extend the conveyor route, move the chest, or add another collection point. Do not assume that increasing signal frequency will compensate for an item that is not nearby.
Nothing in the cited notes says that a timer must pulse at a specific interval. A timer can be part of an automated farm, but the documented condition is simply receipt of a wire signal. If your circuit fires and the chest still does not collect, first verify the signal path and the distance to the drops before changing timing.
Can conveyor belts move items upward in Terraria 1.4.5?
Yes. Desktop 1.4.5.0 adds upward item movement to conveyor belts. The change is recorded in the 1.4.5.0 update notes, and the Conveyor Belts reference documents the belt’s broader transport behavior.
Use belts when the problem is distance or elevation rather than area pickup. A belt can carry an item along a planned path, including an upward section in the 1.4.5.0 desktop behavior. Direction matters: orient each segment so the route leads toward the next collection or storage point, then inspect the endpoint and adjacent tiles to see where items leave the belt.
What happens at the end of a belt?
The conveyor reference explains that an item can drop at the end of a belt or travel a little farther depending on the belt and the surrounding tile placement. That means the final segment is part of the design, not an afterthought. Leave a deliberate landing area, align the endpoint with the chest’s collection zone, and test the transition before enclosing the mechanism.
Can belts cross water or lava?
The mechanics reference describes belts moving items through water and lava where the item survives. This is useful for farms built across liquid-filled terrain, but it does not remove the need to check the belt’s endpoint and neighboring blocks. Survival in the liquid and successful arrival at the intended chest are separate design questions.
What is the difference between a wired chest and a conveyor belt?
Choose the chest when you need a signal-triggered collection action; choose the belt when you need continuous movement along a route. Many farms use both because they solve different parts of the logistics problem.
| Mechanism | Primary job | Activation or movement | Important limits from the documented behavior |
|---|---|---|---|
| Wired chest | Collect nearby dropped items | Requires a wire signal reaching the chest | The notes do not quantify “nearby,” specify item-selection rules, or mandate a circuit layout |
| Conveyor belt | Transport items along a route | Moves items in the belt’s direction; Desktop 1.4.5.0 adds upward movement | Endpoints and surrounding tiles affect whether an item drops or travels farther |
Neither mechanism is universally better. A chest can collect without a long route when drops are already concentrated. A belt can move drops from a distant or elevated source but does not, by itself, establish the chest’s signal-triggered pickup behavior. Evaluate the farm’s shape first: collection area, route length, elevation changes, and where storage must sit.
How do I combine belts and a wired chest in an automated farm?
A combined design has a clear sequence: drops appear, belts move them, and a wire signal activates the chest at the collection point. Build and test each layer separately so a failed pickup is not confused with a routing problem.
- Map the drop area. Identify where enemies, statues, traps, or other farm elements leave items. Keep the map practical: the update only promises pickup of items that are “nearby” to the signaled chest.
- Lay out the transport route. Place conveyor segments from the drop area toward the storage point. For a vertical farm, use the upward-carrying behavior available in Desktop 1.4.5.0, and make the direction change explicit rather than relying on an untested corner.
- Design the endpoint. Decide whether items should fall directly into the chest’s collection area or arrive on a short final belt section. Because endpoint tiles can change how far an item travels, leave room to observe and adjust the landing.
- Install and wire the chest. Put the chest at the intended collection point and connect it to a circuit that can send a wire signal. Keep the trigger accessible while testing.
- Run a small test batch. Drop a few items at the farthest and highest points of the route. Watch their movement, their behavior at the endpoint, and the chest’s response when the signal is sent.
- Scale only after the test works. Add more belt segments or additional collection points after you know which drops reach the chest’s practical nearby area. If a second chest is needed, give it its own clearly traceable signal path rather than assuming one signal will solve every distant pickup.
This staged approach also makes maintenance easier. A belt problem leaves items stranded or redirected; a chest problem leaves nearby items in place after the signal. Checking those symptoms separately is faster than rebuilding the whole farm.
How far away can a wired chest collect items?
The cited 1.4.5.0 notes do not provide a numeric radius. They say only that a chest receiving a wire signal picks up “all nearby dropped items.” The word is therefore a gameplay condition without a published measurement in the source used here.
For planning, measure your own build operationally: place drops at the edges of the intended area, send the signal, and mark which positions are collected. Describe that result as the tested reach of your arrangement, not as an official universal radius. If the farm must cover a broad area, use belts to consolidate drops or divide the area among multiple chests instead of relying on an invented distance.
Why is my Terraria hopper setup not working?
Start with the smallest possible test: one chest, one short wire path, one trigger, and a few dropped items placed close to the chest. Then work outward through the route. The following checks target the documented requirements without assuming an undocumented timing rule.
The chest never reacts
- Confirm that the trigger actually sends a wire signal and that the wire reaches the chest.
- Remove extra components temporarily. A minimal circuit shows whether the issue is the chest connection or a larger farm layout.
- Test with items placed close to the chest. If only distant items fail, the issue may be the undefined nearby condition rather than the signal.
Items move but miss the chest
- Check each belt’s direction and look for a reversed segment.
- Inspect the endpoint and adjacent blocks. The conveyor reference notes that these surroundings can affect whether an item drops or travels a little farther.
- For upward routes, verify that the build is running the Desktop 1.4.5.0 behavior that added upward carrying, rather than assuming every platform build has identical mechanics.
The setup works on one device but not another
Record the platform and exact version before changing the design. The console version history includes a later split-screen hopper-behavior fix, which shows why a console issue can be build-specific; it is not evidence that every console release behaves identically. Check the relevant platform history and reproduce the minimal test on the affected build.
An old guide gives a different belt speed
Be cautious with speed figures copied from older references. The conveyor page ties its speed note to Desktop 1.4.4.9 source code and warns that it may be inaccurate for the stated current desktop version. Use observed route behavior and endpoint testing for a 1.4.5 build instead of treating that older figure as a verified 1.4.5 constant.
Which platforms and versions does this behavior cover?
The release page identifies 1.4.5.0, “Bigger and Boulder,” as released January 27, 2026. The upward-conveyor change is specifically identified for Desktop 1.4.5.0 in the available conveyor history. That qualification matters: do not automatically transfer the desktop change to console or mobile without checking the build you are running.
For platform-specific troubleshooting, note three details in your world’s title screen or version information: platform, full version number, and whether the problem occurs in single-player or split-screen. The console version history records a split-screen hopper fix in a later console patch, so a symptom tied to split-screen may not reproduce in another mode or release.
The safest documentation practice is to label a design “Desktop 1.4.5.0” when it depends on upward belt movement and to describe a chest as “wire-signal pickup” rather than promising a platform-independent hopper block. That wording keeps the build instructions aligned with what the update notes actually establish.
What should a practical 1.4.5 design look like?
For a compact farm, place the chest beside the final drop zone, connect a simple signal circuit, and keep the nearby area uncluttered enough to test. For a tall or spread-out farm, use belts to bring drops toward one or more collection points, using upward sections where the Desktop 1.4.5.0 behavior supports them. In both cases, leave access to the wire trigger and endpoint so you can diagnose the system after expanding it.
Use a written test plan when the farm becomes large: test the farthest drop location, the highest belt segment, the final landing tile, and a signal activation with several items present. Record what happens on the exact platform and version. This produces useful, local knowledge without turning an undocumented radius or legacy speed value into a claim about every Terraria world.
FAQ
Does Terraria have a separate hopper block in 1.4.5?
The documented 1.4.5.0 change describes existing chests responding to wire signals, not a newly named hopper block. “Item hopper” is therefore a convenient way to describe the collection setup, not an official item name established by the update notes.
Can a conveyor belt carry items vertically in every version?
The upward-carrying change is identified for Desktop 1.4.5.0. Platform histories can diverge, so verify the exact console or mobile build before copying a vertical design.
Why do two conveyor layouts with the same endpoint behave differently?
The conveyor reference notes that belt placement and surrounding tiles can determine whether an item drops at the end or travels a little farther. A one-tile change around the endpoint can therefore alter the landing behavior even when the route looks similar.
Is a timer required for chest pickup?
No required interval or mandatory timer layout is specified in the cited update notes. The documented condition is that the chest receives a wire signal; choose and tune the trigger around the farm’s needs, then verify it with a controlled test.
Frequently Asked Questions
Does Terraria have a separate hopper block in 1.4.5?
The documented 1.4.5.0 change describes existing chests responding to wire signals, not a newly named hopper block. “Item hopper” is therefore a convenient way to describe the collection setup, not an official item name established by the update notes.
Can a conveyor belt carry items vertically in every version?
The upward-carrying change is identified for Desktop 1.4.5.0. Platform histories can diverge, so verify the exact console or mobile build before copying a vertical design.
Why do two conveyor layouts with the same endpoint behave differently?
The conveyor reference notes that belt placement and surrounding tiles can determine whether an item drops at the end or travels a little farther. A one-tile change around the endpoint can therefore alter the landing behavior even when the route looks similar.
Is a timer required for chest pickup?
No required interval or mandatory timer layout is specified in the cited update notes. The documented condition is that the chest receives a wire signal; choose and tune the trigger around the farm’s needs, then verify it with a controlled test.