When over the hill multiplayer is not working, the first step is to identify which of two symptoms you have. For a "Failed to join" error after an invite code, the developer asks for a report sent immediately after the failure, including your location and the region of the server you were joining. If clicking Join freezes you on the vehicle screen, a separate demo case points at save-data access, with the developer advising a check of Windows security notifications and OneDrive file availability.
Both paths come from June 2026 Windows demo developer replies, not a release build, and were not independently reproduced. A similar symptom in another build may have a different cause, so treat this as a diagnostic route rather than a universal fix or evidence of a current outage.
Failed to join after an invite code
In a June 13 private-game report, the host sees a friend leave while that friend receives a joining error. The developer suspects a network issue on the joining player's side and asks for an in-game report immediately after it happens, including the player's location and the region of the server they were trying to join.
- Note the exact message and whether you were hosting or joining, and record what the other player saw too.
- Submit feedback from the affected screen immediately after the failure; the demo FAQ says the bottom feedback bar or Ctrl+F sends an error log and a screenshot.
- Include your location and the selected server region.
- If feedback does not work, use the email procedure further down.
A country or broad region is enough to start, and you should not post your street address, IP address or private lobby code publicly.
The demo FAQ acknowledges high-ping issues and recommends a stable connection, but it does not document a required VPN, an exact ping cutoff, router ports to open or a guaranteed region-switch fix. A player's VPN suggestion in the thread is not an official requirement, and the developer's suspected network cause is not proof that every joining error is a network fault.
Join freezes on the vehicle screen
A June 23 to 25 thread describes a different symptom: joining never opens the map, controls become unavailable, and in the original report some single-player interactions also failed, while another participant says single-player worked fine. Keep those observations separate when you describe your own case, because they are not the same failure.
After receiving one player's logs, the developer identified read errors and suspected something preventing the game from creating or accessing save data in Documents\My Games. That is a specific diagnosed demo case, not a confirmed explanation for every stuck lobby.
The developer suspected something was preventing the game from creating or accessing save data in Documents\My Games. — June demo log diagnosis
That diagnosis is why the stuck-screen path leads to file access rather than to networking. It also explains why reinstalling, moving the installation and changing DNS were all reported as unsuccessful in that thread: none of them touches the save-folder access the logs pointed at.
Check security notifications and OneDrive
The developer's advice for the stuck-screen case has two concrete checks, and neither asks you to disable protection.
| Check | What to look for | What it does not ask you to do |
|---|---|---|
| Windows and Defender notifications | An event matching the game's attempted file access | Disable protection wholesale |
| Other security or firewall software | A block or prompt covering the save folder | Turn off the firewall |
| OneDrive-managed Documents | The save folder set to Always keep on this device | Install or enable OneDrive |
The same advice applies to the saved location itself: the official demo FAQ places Windows saves in Documents\My Games\over the hill. Use the save-file location material for locating and backing up files, because this page does not require editing, replacing or deleting a save.
After a relevant correction, retry the same action and note what changed. If it still fails, send fresh logs with the original symptom. Do not assume that a failed check means the save must be deleted, and do not grant broad exclusions when a specific event is what the notification is describing.
Send a useful report even if feedback is broken
If in-game feedback will not open, there is an official alternative. The demo FAQ lists [email protected] for major issues and direct contact, and the developer explicitly requests emailed logs when in-game reporting fails in the stuck-Join thread.
For the Windows demo, the official log directory is:
%USERPROFILE%\AppData\LocalLow\Funselektor\over the hill
Look for Player.log and Player-prev.log there. This is the log directory, not the Documents save directory, and if it is missing you should report your platform and build instead of creating an empty folder or downloading replacement logs. Other builds may use different paths.
| Include | Example of useful detail |
|---|---|
| Build and platform | Your actual version and Windows version; do not label a demo as the release build |
| Joining sequence | Hosting or joining, code entered, button clicked, exact error or last visible screen |
| Comparison | Whether single-player works, and what the host or friend sees |
| Network context | Country or broad location and server region; no public IP or home address |
| Relevant changes | Any security notification found, OneDrive availability checked, retry result |
| Attachments | Player.log, Player-prev.log, requested saves and a screenshot of the failure |
Inspect attachments for personal information and send them privately to official support rather than a public forum. The in-game tool sends a screenshot automatically, so be aware of what is visible in it.
Why the two failures need separate evidence
The connection error and the stuck screen look like one problem and are not. One is a network-flavoured symptom where the developer asked for location and server region; the other is a save-access symptom where the logs showed read errors. Mixing them into a single report makes both harder to diagnose.
| Symptom | Lead path | Key evidence to capture |
|---|---|---|
| Failed to join after an invite code | In-game report with location and server region | Exact error text and both players' view |
| Join freezes on the vehicle screen | Save-data access checks | Player.log and Player-prev.log plus retry result |
If you can enter the world but performance is poor, that is a different task and belongs with PC performance troubleshooting rather than here. If you cannot enter at all, preserve the error and the logs so the developer can tell connection problems apart from local file-access failures.
What this page does not establish
The evidence does not prove a single cause, a repair success rate, a current outage or a release-build fix. It also does not establish that disabling antivirus, deleting progress, forwarding ports or buying a VPN is necessary, and none of those should be presented as the proven solution.
Reinstallation and DNS changes did not solve the reported stuck-Join case, which does not prove they can never help but gives no basis for calling them a fix. If a security notification appears, investigate that specific event rather than granting broad exclusions or turning off the firewall.
What remains unknown before release
Several pieces stay 待确认. Whether the release build changes the joining flow, whether dedicated servers replace the demo's host model, and how crossplay pairing is partitioned are all unpublished. It is also unstated whether the save-access pattern can affect platforms other than Windows, and whether the log directory stays the same once the game leaves the demo.
What you can rely on is the reporting discipline: reproduce the exact symptom, capture the correct evidence for that symptom, and send it through the official channel. That is the one part of this page that does not depend on a future update, and it is the part that actually reaches the developers.