Multiplayer in Over the Hill is more than just two trucks roaring down the same dirt track. The October 14th, 2026 Steam launch introduced a co-op convoy system where two drivers share a single expedition, and getting the basics right early will save you from endless reversing and stuck winches. Whether you are a solo player curious about bringing a friend along, or a returning driver looking for refined etiquette, these over the hill co-op convoy tips will get your crew rolling smoothly through the wilderness.
When planning your route, remember that fuel management is critical—according to the Over the Hill Steam Community discussion, running dry mid-stage is one of the most common reasons convoys fail to reach the extraction point.
Over the Hill Co-op Convoy Basics and Player Counts
The first thing every convoy captain needs to know is exactly how many drivers can join a session. Over the Hill launches as a two-player co-op experience on Steam, with console versions for PlayStation 5, Xbox Series X|S, and Nintendo Switch 2 slated for 2027 according to the official pinned FAQ on the Steam community. The current cap of two vehicles is deliberate: trails are narrow, winch points are limited, and the tuning has been built around a lead-and-support dynamic rather than a free-for-all convoy.
The question of over the hill how many players comes up constantly on the community forums because players see the word "convoy" and assume a longer chain. In practice, you and one friend are the convoy, and the rest of the wilderness is a beautifully empty world of valleys, mountains, and biomes inspired by real-world locations. This small roster has a few important consequences for your planning.
Two-Player Roster vs. Co-op Roles
When a convoy forms, the two drivers are not interchangeable. The game does not assign a hard "leader" tag, but the trails almost always reward a natural split. One driver typically takes the scout-and-spotter role, reading the path ahead and calling out terrain hazards, while the other takes the heavy lifter role, managing winch line placement, fuel, and recovery. The split emerges from gear rather than from any menu, which is why the question of over the hill multiplayer etiquette tends to be answered with "pick a job and stick to it."
The roster also affects save data. Because there are only two slots, shared progress is uncomplicated: the host's world progresses, and the joining player drops in as a guest on that same expedition. This is one of the cleanest things about the launch version of the game compared to larger co-op titles where save syncing becomes a chore.
| Co-op Element | Current State at Launch | What It Means for You |
|---|---|---|
| Max convoy size | 2 players | Plan your role split before driving off |
| Platforms on day one | Steam (PC) | No cross-play until post-launch support |
| Console co-op target | 2027 (PS5, Xbox Series, Switch 2) | Local co-op question is a common forum topic |
| Shared progression | Host world only | Joining player inherits host's discoveries |
| Save behaviour | Per-region, per-host | Switching host starts a new expedition thread |
The two-player cap is also why questions about over the hill split screen keep surfacing. The developer has been asked about local couch co-op repeatedly in the Steam discussions, and at the time of writing, the confirmed answer remains online two-player co-op only. Treat that as the working assumption until a post-launch roadmap post lands.
Roles, Comms, and Real Convoy Etiquette
Once you know the cap, the next layer is the unspoken rulebook. Over the hill multiplayer etiquette is less about hardcoded mechanics and more about the habits you and your co-driver agree on before pulling out of the cabin. The community has converged on a few core patterns that work almost everywhere, and they are worth copying before you invent your own system.
The Three Habits Every Convoy Needs
The first habit is naming the lead. One driver calls the line, the other mirrors. If both drivers are constantly picking alternate paths, the trail gets confusing fast and the winch lines end up anchored to nothing. Pick a lead at the start of each region, and only swap when the route genuinely demands it, such as when the lead gets stuck and the support driver needs to come around for a tow.
The second habit is verbalising the recovery plan before touching the winch. "I'm stuck, I need a tow from the south" is more useful than five minutes of horn honking while your co-driver tries to figure out your orientation. Because the winch cable has a realistic length and snaps under heavy strain, you want both drivers aligned on which anchor point is being used. According to community testing shared in the Steam discussions, convoys that call out the anchor before deploying spend roughly a third less time per recovery.
The third habit is keeping a steady convoy gap. Trail dust, narrow switchbacks, and weather visibility all punish a driver who tailgates. A loose visual gap of around twenty to thirty vehicle lengths is the community sweet spot: close enough to spot a winch target, far enough to avoid rear-ending on a sudden dip. Once the gap is consistent, you can layer shortcuts on top without losing each other.
Common Etiquette Fails to Avoid
Most etiquette issues fall into a handful of repeat patterns. Running ahead without the lead's signal, deploying a winch cable across the partner's line, and forgetting to refuel before a long leg are the three biggest. The game does not punish you for any of these directly, but they each eat expedition time in a way that compounds across a region.
| Etiquette Fail | Why It Hurts the Convoy | Cleaner Alternative |
|---|---|---|
| Speeding past the lead | Triggers dust, breaks the line of sight, may clip partner | Match the lead's pace, especially in fog or dust |
| Anchoring over the partner's winch | Cables tangle, neither driver can recover cleanly | One winch active per recovery, anchor called out first |
| Skipping fuel stops | Both drivers stranded at the worst possible moment | Top off at every cabin, even if the gauge looks fine |
| Hoarding all upgrades | Lead is over-geared, support cannot winch effectively | Split major upgrades between the two drivers |
| Ignoring weather changes | Trail grip shifts, both drivers slide off the ridge | Call out the moment visibility or grip changes |
If you remember nothing else, remember this: the convoy moves at the speed of the slower driver plus the time it takes the lead to set up the next winch. Planning around that compound limit is the single biggest upgrade you can make.
Saves, Progression, and Host Switching
The save system is one of the most-asked-about features in the early-launch community. Over the hill co-op convoy tips only matter if you can actually keep your progress after a session ends, and thankfully the launch implementation is straightforward once you understand the host model. ked-about features in the early-launch community. Over the hill co-op convoy tips only matter if you can actually keep your progress after a session ends, and thankfully the launch implementation is straightforward once you understand the host model. If the host-migration details still feel fuzzy after a few runs, our Over The Hill Playing With A Friend Guide walks through the exact save-state rules and invite flow that determine whether your convoy unlocks carry over to the next session.
How Shared Progression Works
When a convoy forms, the host's world is the source of truth. Discoveries, fast-travel cabins, upgrade tokens, and livery unlocks all live on the host's save. The joining driver brings their own driver profile along, but the expedition's milestones attach to the host's region progress. If the host logs off, the session ends for both drivers, and the joining player reverts to their own solo save next time they boot the game.
According to the official pinned FAQ on the Steam community forums, Over the Hill launches on October 14th, 2026, on Steam, and the developer has confirmed that the same progression model will carry over to the 2027 console versions. There is no region transfer or cloud sync at launch, so the host choice is genuinely a long-term decision, not a per-night one.
Switching Hosts Without Losing Progress
Because the host's save is the expedition record, switching hosts looks like starting a new thread. The new host will have to re-discover the regions from their own cabin, and the old host keeps the discoveries from when they were the lead. Community-tested advice is to commit to one host for the length of a region, then decide whether to switch before crossing into the next biome. This keeps each thread clean and avoids the "we did this yesterday" confusion that catches new convoys off guard.
| Save State Question | Current Behaviour | Practical Tip |
|---|---|---|
| Does co-op progress save? | Yes, to the host's profile | Pick a host that can play regularly |
| What if the host quits? | Session ends, joining driver keeps their solo progress | Plan sessions around the host's schedule |
| Can progress transfer? | No, per host, per region | Re-discover if hosts rotate |
| Is there cloud sync? | Not at launch | Expect local-only saves until post-launch support |
| Does the guest earn achievements? | Host's achievements unlock for the session | Both drivers see the host's stat updates |
The upshot is that host choice matters. If you are the player with the most flexible schedule, volunteering as the host is a quiet way to keep the convoy moving. If neither of you can commit, solo play is a perfectly valid way to learn the trails before forming a convoy later.
Liveries, Mods, and Workshop Support
The livery and modding story is where the community is most active right now, and it ties directly into multiplayer because liveries are one of the first things both drivers see on a convoy. According to the Steam discussions, a dedicated "Custom Livery Modding Documentation" thread is already pinned next to the FAQ, which tells you the developer is treating player-made liveries as a first-class feature from day one.
Livery Sharing Between Drivers
Livery unlocks are tied to the host's save, just like discoveries and cabins. The guest driver will see the host's liveries on the host's vehicle, but the guest's own vehicle retains the guest's livery. If you want matching convoys, the cleanest path is to trade the livery file directly using the documentation in the pinned Steam thread, then each driver applies it on their end. This is the closest the launch version gets to a shared cosmetic economy, and it is much faster than re-unlocking items region by region.
A common misunderstanding is that liveries are region-locked. They are not. Once a livery file is applied, it travels with the vehicle across regions and weather conditions. The only limit is the workshop dependency: if a livery is sourced from the Steam Workshop and the Workshop goes down or is removed, the file may stop loading. Keep a local backup of any livery you care about.
Steam Workshop Support and Mod Plans
Workshop support is the headline mod feature, and it is the reason so many players search for over the hill livery mods in the first week. At launch, the workshop is supported for livery content, with broader mod support rolled out in phases after the release window. The community has been vocal about over the hill workshop support, and the developer has acknowledged in Steam threads that the long-term plan is to expose additional tunable parameters to modders.
The community is also watching closely for over the hill mod support plans beyond liveries. Threads in the Steam discussions cover custom trails, vehicle stat tweaks, and camera mods. None of these are confirmed for the launch window, but the conversation is happening publicly, which is a good sign for the post-launch roadmap.
| Modding Feature | Status at Launch | What Players Want Next |
|---|---|---|
| Livery mods via Steam Workshop | Supported | Already active in community threads |
| Custom decals and paint jobs | Supported | Layered decal support |
| Vehicle stat tweaks | Not at launch | Top community request |
| Custom trails or regions | Not at launch | Long-term modder wishlist |
| Camera and HUD mods | Not at launch | Accessibility and streaming interest |
If you are new to the Workshop, the cleanest first step is to subscribe to a few liveries, launch a co-op session, and confirm that both vehicles render the custom paint correctly. That single test will catch 90% of file-format issues before you invest hours in a custom design.
Putting It All Together: A First-Convoy Checklist
If you only have a single evening to get a convoy rolling, here is the sequence that has worked best for community-tested first sessions. Run through it once, and you will have a reliable template for every future run.
Pre-Drive Setup
Before anyone turns the key, agree on the host. The host's save is the expedition record, and rotating hosts mid-region is the most common cause of "where did we unlock that?" confusion. Once the host is decided, agree on the lead and the support role for the first leg. The lead scouts, the support watches the winch line and fuel. Swap only when the trail genuinely demands it.
During the Drive
Keep the convoy gap at twenty to thirty vehicle lengths, call out the winch anchor before deploying, and refuel at every cabin. If the weather shifts, say so out loud. Trail grip changes in the rain, and both drivers need a moment to recalibrate. When you reach a fork in the trail, the lead picks, and the support mirrors. The lead's job is to commit; the support's job is to keep the lead's options open.
After the Session
End the session at a cabin whenever possible. Cabins are fast-travel anchors, and finishing at one saves you the long walk back to a recovery point. Confirm the host's save before logging off, and screenshot any unlocks you want to reference next session. If you used a Workshop livery, verify that the host's vehicle still renders it after the save reload.
| Checklist Phase | Must-Do Item | Why It Matters |
|---|---|---|
| Pre-drive | Pick host and lead/support roles | Saves are host-based, roles prevent chaos |
| Pre-drive | Top off fuel on both vehicles | Empty tanks in the backcountry are brutal |
| Drive | Keep 20-30 vehicle length gap | Trail dust and visibility are real |
| Drive | Call out winch anchor before deploy | Cables tangle, recovery stalls |
| Drive | Refuel at every cabin | One-stop recovery beats long walks |
| Post-drive | End at a cabin if possible | Cabin = fast travel anchor |
| Post-drive | Screenshot unlocks and liveries | Reference for next session |
| Post-drive | Confirm host save before logging off | Avoid "where did we lose it?" next run |
The checklist looks longer than it feels in practice. After one or two sessions, it becomes muscle memory, and you can start improvising again without losing reliability.
Frequently Asked Questions
How many players can join a co-op convoy in Over the Hill?
The launch version of Over the Hill supports two-player co-op on Steam, which is the official cap for the October 14th, 2026 release. Console versions coming in 2027 will use the same two-player model, and the developer has not announced a larger cap. Treat the cap as a hard limit until a post-launch roadmap confirms otherwise.
Is there split screen or local co-op support?
At launch, the supported co-op mode is online only. Local split screen is a frequently asked question on the Steam community, and the pinned FAQ confirms the current answer is online two-player. If the post-launch roadmap adds local play, it will show up in the discussions thread first, so check there for the most up-to-date status.
Do saves and progression carry over between the two drivers?
Progression is tied to the host's save, which means discoveries, cabins, upgrades, and liveries all attach to the host's profile during a convoy session. The joining driver keeps their own solo save, and switching hosts mid-region effectively starts a fresh expedition thread. Cloud sync and cross-host transfer are not part of the launch feature set.
Can we use custom liveries and mods together in a convoy?
Yes, liveries are supported via the Steam Workshop from launch, and each driver can apply their own livery file independently. Sharing a matching livery is done by trading the file directly using the format documented in the pinned Steam thread. Broader mod support, including vehicle stat tweaks and custom trails, is on the post-launch roadmap but not available yet.
What is the best way to recover when one vehicle gets stuck?
The cleanest recovery pattern is to call out the stuck position and the planned anchor point before deploying the winch. Keep only one active winch cable per recovery, and have the support driver position downslope so a tow is possible if the winch snaps. Refuel at every cabin, and avoid anchoring over your partner's line to prevent the cable tangles that eat the most expedition time.