Moonlight Peaks July Patch Round-Up: Controller, Save & Quest Fixes
A platform-by-platform round-up of Moonlight Peaks' July 2026 fixes: controller inputs, Loveage and story progression, Vampster achievements, performance, and Google Play Games save recovery.
Moonlight Peaks received a rapid series of post-launch updates through the second half of July. The practical headline is not a single universal version number: Steam, Switch, Switch 2, and Google Play Games have different current builds and different fixes. If an old post says a quest, controller, or save issue is still unavoidable, check your platform’s version first.
Marvelous’ official patch log currently lists 1.1.45 on Steam, 1.1.46 on Switch and Switch 2 in North America and Europe, and 1.1.51 on Google Play Games. This article is a reading guide to those official notes, not a substitute for the version displayed by your own storefront.
The fixes most players will notice
The July updates focused on the rough edges that interrupt a normal night in town: loading, controls, storage, event progression, and collections. The July 15 update included loading improvements, fixes for full-storage plots and quick transfers, and a Steam controller fallback correction. The next day’s PC update addressed issues around the embroidery table, post-house-upgrade loading, tree-seed planting and season information, placement returning objects to inventory, crops on rainy nights, and a Steam save corruption case caused by closing during a save.
On July 21, the patch list broadened again. It includes a photo-sensitivity warning, a widescreen fix for Stargazing, a fix for the Loveage Gift Exchange softlock, and repairs for several progression blockers. The official notes say that a stuck Recover the Moon quest should advance automatically on the following in-game day, while Back to the Den can now unlock retroactively after all Vampsters are returned and another in-game day passes.
Those distinctions matter. A general statement that “the quest is fixed” is not enough for a player who is on a different platform or has not advanced the in-game clock. Use the exact condition named in the notes, save normally, and update before trying to reproduce an issue described in a launch-week video.
Controller and interface changes
Two controller fixes are especially relevant to handheld and console players. The July 15 notes name a fix for the Steam controller fallback, while the July 29 Switch and Switch 2 release explicitly fixes the L and R buttons. If a bumper no longer changes a tab or opens the expected view, install the available console update before remapping buttons or assuming the input is intentionally different.
The July 21 update also lists performance work for bee houses, the firefly sanctuary, areas with many interactables, Farm Helpers, and item pickups. These are specific fixes, not a publisher guarantee of one frame-rate or loading-time figure across every device. A helpful support report therefore includes the platform, game version, location, and action that produces a remaining slowdown.
For current setup advice, see our refreshed Controls & UI guide, Steam Deck guide, and Nintendo Switch & Switch 2 guide.
Event, quest, and collection recovery
The official list gives three useful recovery paths without asking players to gamble on unofficial save edits:
- Loveage Gift Exchange: Update first. The July 21 notes identify a softlock fix; then follow the event’s Saturday selection and Sunday exchange order in our Loveage Festival guide.
- Recover the Moon: If you were stuck, let the next in-game day begin after updating. The patch says the quest should proceed automatically in that case.
- Back to the Den: After returning every Vampster, advance one in-game day. The July 21 release says the achievement now fires retroactively; our Soul Blobs & Vampsters guide explains the collection separately.
The point is to distinguish a patch-defined next step from a workaround that merely happened to help one person. If the named step fails, do not repeatedly force-close the game during a save. Record the version, game day, and last completed interaction, then use the publisher’s support route with that reproducible information.
Platform status at the end of July
| Platform | Official version listed | Relevant late-July note |
|---|---|---|
| Steam | 1.1.45 | Performance and progression fixes from the July 21 update. |
| Nintendo Switch | 1.1.46 (NA/EU) | Prior fixes plus the L and R button correction. |
| Nintendo Switch 2 | 1.1.46 (NA/EU) | Same listed console update and shoulder-button correction. |
| Google Play Games | 1.1.51 | Fixes an infinite launch load and a cloud-save failure/lost-progress issue. |
Google Play Games players should pay special attention to the final row: version 1.1.51, dated July 31 in the official post, targets an infinite loading screen at launch and a cloud-save failure that could lead to lost progress. That is a platform-specific correction; it should not be read as a promise about Android phones or other storefronts not named in the note.
What to do before reporting a bug
Start with the current patch and the default controls. Then reproduce the issue once in a normal session, noting whether it happens in a particular area, during a specific quest step, or after a particular menu interaction. Avoid claiming a fix has failed merely because a different build, region, or in-game condition behaves differently.
We will keep the evergreen guides linked above updated when Marvelous publishes another named platform release. For now, the official July log is the reliable baseline: it confirms that several frustrating launch-week blockers have fixes, while also making clear that the latest version is not identical everywhere.