Hitting the trails with a full crew turns a relaxed off-road cruise into the real over the hill experience, which is exactly why this over the hill how to play with friends walkthrough exists. According to the official store page, the game runs just as happily for a lone driver as it does for a convoy of up to four, with groups sharing the pretty stretches and the tougher routes while they pull each other out of trouble, lay planks across gaps, and agree on a direction. Multiplayer is the intended way to play for most groups, but the invite flow, crossplay support, and shared progression rules catch a lot of new drivers off guard. This guide walks through the Steam invite steps, what to expect from a four-player session, and how to make sure your co-op progress sticks.
According to the Steam Community discussions, Over the Hill supports up to four players in co-op across both online and local multiplayer modes, with each player controlling a unique animal navigating the game's physics-based levels together.
Multiplayer sessions are typically hosted by the player who owns the base game, while friends join through their own copies of Over the Hill to participate in the shared co-op campaign, as confirmed in the Steam Community discussion for Over the Hill.
Pre-Flight Checklist Before You Form a Convoy
Before anyone loads into a truck, the host needs to confirm a few basics so the session does not collapse the moment the first trail loads. Over the hill runs on Steam, so the entire invite flow goes through Steam's overlay, friends list, and session browser — there is no in-game matchmaking queue to lean on, and there is no built-in lobby code system at launch.
| Requirement | What to Confirm | Why It Matters |
|---|---|---|
| Steam client updated | Latest stable build | Avoids overlay and friends-list desync |
| Same game version | All clients on the same patch | Mismatched builds cause silent kick |
| Stable connection | Wired or strong Wi-Fi | Host migration is not guaranteed |
| DLC parity | All players own the same DLC | Optional content can lock players out |
| Region proximity | Closer regions = lower ping | Voice chat and physics stay in sync |
Crossplay is the most-asked question that new drivers raise. According to community reports, over the hill cross platform support currently applies between Steam and any other PC storefront the game ships on, while console parity is on the official post-launch roadmap rather than shipped today. Players on consoles will need to wait for the corresponding console update, and they cannot join a Steam-hosted session in the meantime. The simplest rule of thumb: if everyone is launching the same PC build, you are clear to invite.
Confirming Crossplay and Region Status
A quick way to confirm crossplay is to check the friends list entry for each invitee. If Steam shows them as playing the same build of over the hill, the invite handshake will succeed — if their status shows them in a different version or the title does not appear in their library at all, the invite silently fails. Region mismatches usually appear as a "could not join" error rather than a full disconnect, so do not assume a broken invite means the friends list is wrong.
Sending the Invite: Steam Setup From Both Sides
The actual hand-off of the convoy happens through Steam's normal invite flow, which works the same whether you are hosting a casual convoy or coordinating a full challenge trail. The host opens the friends list, sees their partner's status, and fires off a join request; the invitee accepts, and the session pulls everyone into the same world.
| Step | Host Action | Invitee Action | Result |
|---|---|---|---|
| 1 | Launch over the hill from Steam | Launch over the hill from Steam | Both clients connect to Steam overlay |
| 2 | Open Shift+Tab friends list | Wait for invite | Host sees "Invite to Game" option |
| 3 | Right-click friend → "Invite to Game" | Accept incoming invite | Invite counter appears in client |
| 4 | Confirm "Join Session" prompt | Click "Join" | Both load into host's world |
| 5 | Repeat for up to 3 more friends | Repeat for remaining slots | Full 4-player convoy rolls out |
If a friend does not see the invite, the most common cause is that they launched the game outside of Steam — for example through a desktop shortcut that bypasses the client. Both sides need to start the game through Steam proper for the overlay and friends handshake to work. A second common failure is overlays from other tools (Discord, MSI Afterburner, RGB software) blocking the invite dialog; disabling those for the session usually clears it.
What If Your Friend Is Already Driving?
Joining a friend who is mid-run is supported. Your friend becomes the host automatically when you connect, and their active convoy, cabin, and unlocked upgrades carry over. If you want to learn more about the join flow specifically, the over the hill how to join a friend guide walks through the mid-run scenarios in detail, including how to handle a stranded friend on the trail.
Building a Stable Four-Player Co-op Session
Once everyone is in the same world, the goal is to keep the convoy rolling. Stability in over the hill multiplayer is mostly a function of connection quality, host hardware, and how the crew uses the radio layer. Most disconnects happen early, while everyone is still figuring out their setup, and become rare once the group settles into a rhythm.
| Stability Lever | Recommended Setting | Common Pitfall |
|---|---|---|
| Host internet | Wired Ethernet, <50ms ping | Wi-Fi with weak signal |
| Player count | 2–3 for learning, 4 for full convoy | Jumping to 4 on day one |
| Voice channel | Steam voice or Discord | Both at once causes echo |
| Session length | 1.5–2 hours per sitting | Marathon sessions and host fatigue |
| Mod parity | Same mods enabled for all | Host has mods, client does not |
Voice chat inside over the hill uses an in-game radio layer, which is great for immersion but is not a substitute for a real voice channel when coordinating a recovery. A practical setup is to keep Discord or Steam voice running for crew coordination, mute the in-game radio for non-essential chatter, and only use the radio for roleplay moments on the trail. That way the radio stays in-world for flavor, but the actual callouts stay clean.
Tuning the Convoy for Longer Runs
For long convoy runs, the host should consider locking the session so random players cannot drop in. According to community testing, leaving the session open invites rubber-banders and griefers, especially on popular servers, while a private session keeps the crew tight. If a player drops mid-run, the host can invite a replacement, but everyone should agree to a short grace period before the replacement takes over the dropped player's truck — the over the hill playing with a friend guide covers how to recover and rebalance after a mid-run dropout.
How Multiplayer Progression and Saves Actually Work
Multiplayer progression is the question that catches most new crews off guard, and the answer is more nuanced than the steam forums make it sound. Over the hill multiplayer progression is shared at the convoy level for some things and personal for others, and figuring out the split before you start saves a lot of confusion later.
| Progression Type | Shared in Co-op? | Notes |
|---|---|---|
| Trail completions | Yes | Counts toward convoy achievements |
| Pebble currency | Split | Each player collects independently |
| Vehicle unlocks | Personal | Garage carries to solo runs |
| Cabin unlocks | Shared | Fast travel becomes group-wide |
| Achievements | Per-player | Each client earns their own |
| Cosmetic drops | Per-player | Loot is not pooled |
So the short answer to "does co-op progress save" is: yes, but the way it saves depends on what kind of progress you are talking about. Trail completions, region exits, and cabin unlocks all stick on the host's world, so the next time the host launches the game alone, those unlocks are still there. Pebbles, vehicle unlocks, and achievements are saved per-player, which means each crew member can pop into solo play and keep building their own garage without losing anything they earned in convoy.
Why Host Switching Matters
When the host leaves the session, the game needs to migrate the world state to whoever takes over. According to community testing, host migration works smoothly when a player with an active connection takes over, but it can stutter or fail if the replacement has a flaky network. A reliable habit is to designate a backup host before the convoy rolls out — usually the player with the most stable connection — so the swap does not catch anyone off guard. If you want a deeper look at how save data and cloud sync work between PC and console versions, the over the hill cross save guide covers the full picture.
Common Pitfalls and Quick Fixes
Most over the hill co-op headaches fall into a small handful of repeatable issues. Running through this short list before each convoy saves the first thirty minutes of the session, which is the part of the night that is most likely to break flow.
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
| "Could not join friend" | Different game version | Verify both clients on same patch |
| Invite never appears | Launched outside Steam | Restart from Steam client |
| Rubber-banding on trail | Host on weak Wi-Fi | Switch host to wired connection |
| Voice echo | Both Discord and radio open | Mute one channel |
| Player invisible on map | Stale invite | Re-invite from friends list |
| Host migrated to AFK player | No backup host | Designate replacement before run |
| Achievements not unlocking | Achievement flag delayed | Return to cabin, wait 30s |
A surprisingly common trap is the "AFK host" problem — if the host walks away from the keyboard mid-run, the session can become unstable, and the migration target defaults to whoever joined most recently rather than whoever is most stable. Calling out a backup host at the start of every run eliminates this whole class of issue.
Etiquette That Saves the Run
Convoy etiquette is the part nobody writes a guide for but everybody notices when it is missing. The three habits that keep a four-player run healthy are: call out your route before you commit, drop planks and winches for the player behind you, and never rage-quit mid-trail. Each one sounds obvious, but the moment a convoy hits a difficult river crossing or a steep climb, the crew that follows those three rules finishes while everyone else disconnects. If you want a more structured look at convoy roles and what each driver brings to the table, the over the hill playing with a friend guide has a full breakdown.
Frequently Asked Questions
Can I play over the hill online co-op with random players?
The current build focuses on invite-based play through Steam's friends list, with no built-in public matchmaking queue at launch. Community-run Discord servers sometimes coordinate random crews for specific trails, but the safest path for a stable session is a private invite between friends on the same game version.
Does over the hill is there crossplay between PC and console?
As of the latest community report, crossplay is supported between PC storefronts that share the same build, while console parity is on the post-launch roadmap. Console players cannot join a Steam-hosted session until their platform update lands, and vice versa.
Will my over the hill multiplayer progression carry to solo runs?
Trail completions, cabin unlocks, and region exits are saved on the host's world and carry into solo play, while pebbles, vehicle unlocks, and achievements are saved per-player. That means each crew member can pop into solo mode and keep building their garage without losing anything they earned in convoy.
How many players can join one over the hill session?
The maximum is four players per session, including the host. Smaller crews of two or three are easier to coordinate on technical trails, and the full four-player convoy is best saved for routes the group has already cleared at least once.