The first bad decision in The Mound: Omen of Cthulhu often happens before anyone reaches the jungle. One explorer takes the only firearm and its ammunition, another fills every slot with ship supplies, and nobody agrees on how much treasure is enough. The contract is signed, but the expedition has no division of labor and no retreat condition.
This launch guide fixes that sequence. It covers the Galleon setup, a repeatable wagon-centered expedition loop, the choice between completing a contract and leaving with a partial haul, and the verified route to the Fort Logbook on the second expedition. It does not pretend that one fixed path solves the later contracts: the jungle changes pressure through noise, weather, enemies, and private hallucinations, while the written launch references currently support only the opening and Fort route in reliable detail.
Launch boundary: this route was checked on July 18, 2026 against Steam AppID 2569760, three days after release. ACE Team is the developer and Nacon is the publisher. The current game supports solo play and online groups of up to four, but a July 17 test branch is already previewing inventory, configuration, balance, and quality-of-life changes. Follow the prompt and mission values shown by your client rather than memorizing a number from a launch-day run.
Turn the contract into a return rule
At the table beside the Captain, do not sign after reading only the reward. Check four connected facts: the named objective, any required treasure value, the shared equipment provided, and the available destination. A run can collect attractive loot and still miss the requested object. It can also find the object while remaining short of the value shown on the contract.
Set the retreat rule while the deck is quiet. A useful first-session version is:
We return when the contract objective and displayed value are secured, or earlier if the party can no longer protect the wagon and the route back.
The second half matters because the Boatman can end an expedition even when the contract is unfinished. An early withdrawal sacrifices the normal completion reward, but it can preserve part of the haul and turn a collapsing run into information for the next attempt. The launch version also removed the old mandatory mission time cap, so “we are still allowed to stay” is not a reason to keep pushing.
Build one shared loadout in four parts
After signing, collect the supplies behind the Captain, but leave room for the objects that actually satisfy the mission. In solo play, a melee weapon, a ranged option, ammunition, and recovery food form a practical baseline if the contract offers them. In a group, distribute functions instead of giving everyone a smaller copy of the same kit:
- Quiet contact: carries the melee or silent option and handles ordinary threats without turning every encounter into a gunshot.
- Emergency range: holds the firearm and matching ammunition for a confirmed threat, not for every shape in the fog.
- Light and recovery: keeps the lamp, food, bandages, or other rescue utility available when the route becomes dark or somebody goes down.
- Wagon and objective: protects free carrying space, banks idols and contract objects, and calls the return before the other roles become separated.
These are temporary jobs, not character classes. If the contract provides only one pistol, there is only one ranged emergency role. If it offers different tools, rebuild the jobs around that table. The July 15 launch update also added a combat guidebook at the practice dummy and a weapon-upgrade anvil on the ship; check both before spending Tokens or assuming a familiar weapon still behaves exactly as it did in the demo.
Return to the Captain’s table, select the landing area on the map, then stand inside the marked departure space near the rowboats. The countdown begins only when the expedition is ready to leave. If somebody is still sorting the wagon or has taken ammunition for a weapon they do not carry, step out and fix it now.
Move in loops that always touch the wagon
The safest opening pattern is not a straight charge from the beach. Scout a short branch, recover one meaningful object or a manageable group of valuables, return to the ox wagon, check the mission state, and then choose the next branch. Tulu-metal artifacts and large idols compete with a small personal inventory; put them in the wagon instead of carrying them through every fight.
The wagon also leaves a visible painted line along its route. When the terrain folds back on itself, that trail is more reliable than remembering which identical patch of vegetation was “left” on the way in. Before committing to a ruin or upper path, identify where the paint meets the route home.
Use the medallion with the same discipline as a firearm. Striking it can reveal the direction of hidden Tulu-metal treasure, but the clang is not private. The developers explicitly frame the sound as a risk that can alert the jungle. Ring it when the group is together, has a defensive position, and is prepared either to follow the signal or abandon it. Repeatedly testing it while split up trades ammunition and sanity for a direction nobody is ready to use.
The current expedition guide also reports that returning to the wagon helps reduce insanity. Treat that as a regroup checkpoint rather than an invisible cure: bank the object, compare what each player saw, confirm the painted route, and decide whether the next loop is still part of the contract.
Use three questions before taking one more branch
| Question | Continue only when | Begin extraction when |
|---|---|---|
| Is the contract already safe? | The named objective or required value is still missing and the next search area is reachable. | The objective and displayed value are banked; everything else is optional risk. |
| Can the team verify reality? | Players remain in voice or visual contact and agree on the route and threats. | Figures, sounds, or paths cannot be cross-checked, or a fractured player is making solo decisions. |
| Can the return survive contact? | A quiet weapon, emergency range, light, and recovery are still usable. | Rain has compromised gunpowder, ammunition is nearly gone, or repeated fights have consumed the recovery margin. |
Noise connects all three questions. Sprinting, cutting through branches, gunfire, and the medallion can raise the jungle’s attention. Rain adds another constraint because wet gunpowder can make period firearms fail. When the weather turns, the bow or melee tool stops being a backup and becomes the dependable route home.
Reach the Fort Logbook by going around the gate
The second expedition asks for a Logbook in a map full of loops and elevation changes. The dependable landmark chain is left tent, circular beach rock, uphill path, locked gate, ladder, cave, fallen-tree lantern, altered camp. Use those objects instead of compass headings.
From the boats to the locked gate
- Move slightly inland from the landing, then turn left immediately. Search the tent for the medallion.
- Continue along the coast until a circular mass of rock divides the beach route. The right side contains a statue that baits a concealed pit; the left side is the safer approach and has a chest. An idol also sits behind the rock.
- Take the path climbing away from the shore. Follow the ramp around to the right and cross the straight grassy section.
- Clear or bypass the first undead threat, then give the heavier enemy ahead enough distance. It can lunge and knock an explorer down, creating time for the jungle to close around the party.
- At the far end, move to the left side of the area and locate the Fort gate. Do not spend time looking for a front-side switch; this gate opens from inside.
Use the ladder, cave, and fallen tree
Face the locked gate and look left for a small cliff with a ladder. Climb it and follow the upper route. There is an idol on the left. Farther ahead, a cave contains another undead enemy and another idol, but the cave is a side check rather than the Fort entrance.
Back out of the cave and look left. A lantern beneath a fallen tree marks the continuation. Pass under that tree to reach the camp. When you drop into it, a flash can replace the familiar scene with a darker version. Do not sprint back into the jungle or fire at the first unexplained shape. Hold the camp for the distortion to clear; the normal layout returns after a short interval.
Carry the Logbook instead of equipping around it
Search under the tent after the camp returns to normal. The Fort Logbook occupies the explorer’s hands. Switching to another equipped item drops it, although the carrier can still collect nearby loot. Assign somebody else to lead fights and interact with emergency tools while the carrier keeps the book visible.
Open the Fort gate from the inside, descend toward the shore, and return to the boats on the left side of the beach. Check the live contract before departure: the Logbook may be the named objective while a separate treasure quota still needs attention. If value is short but the carrier is stable, make a small wagon-centered loop. If the route or party has deteriorated, preserve the objective and leave instead of turning the successful Fort entry into an unnecessary wipe.
Make hallucinations answer a fixed protocol
Different explorers can receive different sights and sounds. A threat visible to one player may not exist for another, and a familiar silhouette is not automatically a real teammate. Long debates are useless when an armed player is already aiming, so agree on three short checks before departure:
- Confirm sight: describe the object and landmark without telling the other player what answer to give.
- Confirm position: make the supposed teammate answer from a known location, preferably the wagon or another visible anchor.
- Confirm action: one player moves or uses a harmless signal while the observer checks whether the figure responds correctly.
A player who fails those checks should stop leading navigation and targeting until the group reaches the wagon. This is not passive play; it protects the contract from the game’s most dangerous false information. In solo mode, the launch build provides commands that switch the bot companion between silent weapons and a noisier rifle. Use the quiet setting while scouting and reserve the rifle command for a threat you have already confirmed.
Keep the whole party on the same July build
Nacon’s July 17 notice opened a Steam test branch for the first post-launch patch. It previews keyboard-and-mouse inventory changes, a startup camera preset, server-password support, balance adjustments, and other fixes. Crossplay is disabled on that branch, and players on different branches cannot join one another. Before diagnosing a missing friend or a changed inventory behavior, compare the selected branch and game version across the squad.
The normal launch build also has a crossplay invitation issue: the official July 15 notes recommend finding the host through the server list while invitation reliability is being repaired. Those details are temporary. Check the current official patch notes before treating either workaround as permanent.
Watch the systems collide in the developer showcase
ACE Team art director Edmundo Bordeu narrates this uncut expedition. The footage is useful for seeing how quickly a clean search becomes a sanity, noise, and extraction problem. Steam’s official announcement identifies the video, and YouTube independently confirms the title and Nacon channel.
If the Fort Logbook is in one explorer’s hands, the inside gate is open, and the boats are reachable on the left side of the shore, the second expedition’s hard navigation problem is solved. The remaining decision belongs to the live contract card: cover any required value with the smallest safe loop, or take the book home before the jungle turns a completed objective into another body.
Sources & credits
Game identity, Steam AppID 2569760, ACE Team and Nacon credits, July 15, 2026 release, solo and up-to-four-player scope, launch changes, current patch boundary, contract design, weather and noise behavior, the official gameplay showcase, and all four original 1920-by-1080 JPG images were verified against the official Steam page, the developer announcement feed, and the official Nacon page. Galleon preparation, wagon use, retreat decisions, and the Fort Logbook route were reconciled across readable launch guides. Warning-marked, verification-blocked, pre-release, derivative, and uncorroborated wiki-style sources were not used for route facts.