The Mound June 18 Demo Patch Notes Explained

Changes that were live in the demo build

ACE Team posted a new Steam Next Fest demo build on June 18, 2026. The patch made corpses more useful by allowing direct weapon looting, added two sanity effects and placed discoverable guidebook codex pages across the mainland.

Resource availability also changed: ammunition pickups carried more bullets, undead enemies had a slightly higher chance to drop ammo, and selected areas received more weapons and ammunition. The appraiser evaluated returned gear more favorably.

Accessibility and interface

The update added a subtitle font-size option and several interface visual improvements. Huemul behavior was improved. These are especially relevant in a game where readable communication and recognizing a real object during hallucinations matter.

Bug fixes

• Token debt was removed.
• Stretched polygons in the onboarding area were fixed.
• First-person characters crouched correctly while picking up bodies.
• Missing forest-state time warnings were restored.
• The Map item stopped behaving like the Medallion.
• Several smaller issues were addressed.

Announced work was not part of that patch

The developer follow-up discussed a weapon-blocking system, a less absolute replacement for the hard level timer, weapon upgrades, better melee durability and an option to disable mouse smoothing. ACE Team explained that blocking required careful balance because a lone player should still feel vulnerable.

Those items were at different development stages. Do not read the June 18 patch list as proof that all of them shipped in the launch build.

What this means for players

Returning demo players should recheck weapon and ammo expectations: corpse looting and larger drops can change early route planning. New codex pages add reasons to extract even when the contract quota is missed. If you are troubleshooting the full release, compare your current version notes with this demo list before assuming a June fix still behaves identically.

The practical way to use this page is to turn its source facts into a run plan before the party leaves the safe start. For demo patch june 18, that means naming the objective, deciding who carries light, deciding who watches the return line, and agreeing on the first reason to extract. The Mound Omen of Cthulhu repeatedly makes small mistakes compound: one loud movement draws attention, one player chases an unconfirmed sight, one extra room moves the group away from the cart, and a useful run becomes a loss. A cautious team can still take risks, but the risk should have a named purpose.

Use a three-question check whenever the run becomes uncertain. First, what does the contract still require? Second, what value or evidence has already been secured? Third, can every player explain how to reach the cart or boat line from the current room, path, or clearing? If the team cannot answer all three, the next action should be a reset rather than a deeper push. This is especially important because hallucinations can differ between players and because the reviewed material describes enemies, noise, and madness as pressure systems that punish isolated reactions.

For planning purposes, separate hard facts from useful inferences. Store pages can prove platform labels. Official announcements can prove developer statements and dated patch notes. Transcripts can prove described systems when the speaker clearly names them. Visual gameplay can prove what appears on screen, such as expedition pacing, a cart route, or preparation aboard the Tempest, but it should not be treated as proof of invisible formulas. This distinction matters because The Mound Omen of Cthulhu is still best served by honest guidance. A page that admits uncertainty is more useful than a page that invents a best route.

The safest repeatable pattern is scout, confirm, bank, and leave. Scout the first leg quietly. Confirm any strange sight or sound with the team. Bank value, information, or objective progress at the cart when the route allows it. Leave once the run has enough progress to justify the risk already taken. Players looking for a perfect clear can still choose a deeper push, but they should do it with the cost named in advance: ammunition, durability, time, noise, sanity pressure, or the possibility of losing a teammate far from help.

When playing with new teammates, keep vocabulary short. Use "cart," "boat," "objective," "value," "noise," "vision," and "extract" instead of long explanations during a scare. Those words map directly to the decisions this wiki can support. The same vocabulary helps solo players as a self-check: if you cannot name the next objective, the nearest return line, and the condition that would make you leave, you are probably exploring from momentum rather than from a plan.

June Patch Applied Checks

June Patch decisions start with subtitle option and corpse loot. treat the patch as dated history; cite the discussion for changed behavior. If demo fix conflicts with feedback note, send access checks back to the store. This keeps the page useful while avoiding claims that the reviewed material does not support.

Use this article beside the live source list as a small decision sheet. Record the current build, platform page, video timestamp, or teammate report before changing the plan. When the evidence is dated, treat it as a snapshot; when the evidence is visual, describe only what appears on screen. The result is a practical The Mound Omen of Cthulhu answer that stays anchored to the specific reader intent for june patch.

For the June 18 demo patch, the most useful reader action is comparison. Check whether corpse weapon looting, sanity effects, codex pages, subtitle sizing, and the removed Token debt are visible in the build you are actually playing. If a later full-release patch changed the same system, treat the June note as history rather than a current rule. That keeps troubleshooting honest and prevents a dated demo fix from being mistaken for permanent launch behavior.

What to test after reading the note

Turn the June 18 list into a short in-game checklist instead of assuming every line applies forever. In a demo build, verify whether corpses can provide weapons, whether ammunition pickups feel larger than earlier reports, whether guidebook codex pages appear on the mainland, and whether subtitle size can be changed in the options menu. In the full release, use the same items as comparison points, then defer to any newer patch note if behavior differs.

The announced future work should be handled separately. Weapon blocking, time-limit changes, weapon upgrades, melee durability improvements and mouse-smoothing options were discussion items, not guaranteed June 18 fixes. For those systems, look for a later dated note or the option inside the current game client before changing expectations.

Source

• Developer's Steam discussion and patch note