Farlands Bugs & Fixes: Wedding & Sprinkler Fixes in 1.0.4, Crash Workarounds

Farlands known issues after patch 1.0.4: the wedding event and sprinkler bugs fixed, the day-3 end-of-day crash workaround, EA save achievement pops, and controller/Steam Deck limitations.

Last updated: 8/7/2026

Quick Answer: Update to 1.0.4 (August 5). It ended the launch window's two longest-running blockers: the wedding event that never triggered and the sprinklers that didn't water. A player stuck on the wedding bug since July confirmed the fix works even on an already-broken save. The most impactful issue still live is the end-of-day crash, which can eat a day's progress and has a community workaround: let the sale summary finish listing, then click through with the mouse.

Version note: Status current as of August 7, 2026, on patch 1.0.4. Assembled from the developers' official patch notes and known-issues list, launch-week Steam reviews, and player-confirmed workarounds on the community forums, linked inline.

Patch 1.0.2 (July 17): What It Fixed

The first post-launch patch, one day after release. Highlights from the official notes:

  • Item counting when picking up multiple units of the same item.
  • Fishing-related issues (the notes don't itemize which).
  • Speeder event fixes: player starting position, ship panel, animations, tutorial button prompt, overall behaviour.
  • Event fixes: Iriel and Te'Kragh no longer stuck in fixed positions; the Nori and Amadeus event now requires two free inventory slots before it triggers; an Ark event trigger was moved so it can't overlap a delivery; no more moving during post-donation dialogue.
  • UI and quality of life: load slots show progress info and icons, the options menu behaves better when configuring controls, exit buttons standardised, missing Chinese/Japanese font characters added, duplicated Chinese dialogue fixed.
  • World fixes: collisions in Darmstad (water and oxygen areas), map boundary in the Darmstad mine, Vanadian layer/pyramid display, and removal of a cut Early Access insect (the Vanadian wasp) that was still spawning.

Not mentioned in 1.0.2: the end-of-day crash, the Ark/museum donation crash, and controller/Steam Deck support.

Patch 1.0.3 (July 23): What It Fixed

  • Crafting with a full inventory no longer eats items. Crafting is blocked until you have room.
  • "Harvest all vegetables" now awards correctly. If you'd grown everything and Natural born farmer never popped, that was this bug (Achievements Guide).
  • Dialogue fixes, including freezes when talking to some characters. This may not have caught everything β€” see the section below.
  • Fishing: taking damage now interrupts the fishing action.
  • Matter processor can no longer be closed until its progress bar has stopped.
  • End-of-day window displays earnings correctly. A display fix only; the end-of-day crash below is a separate problem.
  • NPC fixes: Elliot's farm sprite, Zoe's path no longer overlapping Gorg, NPCs no longer blocking entrances, Layla now gives 1 typewriter instead of 10.
  • Romance rebalance: relationship points rebalanced so it costs less to improve relationships (Romance Guide).
  • UI and other: close buttons in all windows, travel panel on ultra-wide monitors, controller navigation in the relationships window, Icomelon recipe added, ship interior lighting.

Not mentioned in 1.0.3: the sprinkler known issue, the end-of-day crash, the Ark/museum donation crash, and controller/Steam Deck support.

Patch 1.0.4 (August 5): What It Fixed

The most consequential patch since launch β€” it clears both of the bugs this page had been tracking longest.

  • Weddings work in Terbin and Galea, and Spike's and Eddy's event 5 now triggers correctly. That is the wedding blocker, named directly (section below).
  • Sprinklers water correctly, plus a fix for multiple sprinklers deleting seeds after placement (section below).
  • Other event repairs: tables reactivate after Siona's event, Alisha sends the correct email after hers, and Siona's cake email actually contains the cake.
  • Farm handling: removing tilled soil that still holds a seed, and the energy drain from watering an already-watered tile.
  • Inventory: cheaper pickups when the inventory is full, a check for zero-count stacks, items can no longer be placed in unavailable areas, the crafting machine now counts across multiple stacks, and the crystal bee drops to the ground instead of vanishing when your bags are full.
  • Mines and enemies: mine stairs work as intended, and defeated enemies are removed properly along with their sound effects.
  • Economy: balloon sale value cut so it no longer breaks the economy.
  • Stability: more robust loading of Ark donations, and you can no longer talk to Bob while he's hiding in the arena.

Still not mentioned in 1.0.4: the end-of-day crash, the 2 AM soft lock, and controller/Steam Deck support.

Blacksmith Missing / Can't Upgrade Tools β€” Fixed

Through late Early Access, the blacksmith who handles tool upgrades could disappear from saves entirely, blocking tool progression. It survived restarts and reinstalls and it was the community's number one complaint.

Status: fixed. The developer (posting as EricRod) confirmed on July 7, 2026 that the bug "should now be fixed," with an apology acknowledging it "was actually affecting far too many players." Players in the fix thread confirmed it works.

If yours is still missing at 1.0: update the game, verify local files through Steam, then report it in the pinned "Known issues" thread. You'd be an edge case worth the developers' attention.

End-of-Day Crash (Day 3 Crash) β€” Workaround Confirmed

Symptom: the game crashes during the end-of-day sequence, for several players reliably on night 3, wiping the day's progress each attempt. One reviewer replayed day 3 five times.

Workaround: on the end-of-day summary, wait until all sold items have finished listing, then advance with a mouse click. The crash appears connected to controller input on that screen, and players who switch to the mouse for that one interaction stop crashing.

Status: live at 1.0 for some players. Patch 1.0.3 fixed the end-of-day window's earnings display, but neither patch mentions this crash. If it persists even with the mouse, report your specs in the pinned bug thread.

Soft Lock Around 2:00 AM

Symptom: if a screen transition overlaps the game's 2 AM forced-sleep moment, the game can lock up entirely. The clearest report: returning from the rainbow planet to the ship, the black-screen transition collided with the 2 AM pass-out, leaving the player unable to move or open the menu.

How to avoid it: start heading home or trigger sleep well before 2 AM, and don't take planet-to-ship transitions in the final minutes of the day. There's no in-game escape once you're locked β€” you have to quit, which costs the day, the same way the end-of-day crash does.

Three more triggers from one player's experience: entering and exiting farm buildings too fast can teleport you out of bounds until the 2 AM pass-out; entering a new area right at 2 AM can leave the character stuck without ever passing out; and interacting with a destructible object during the pass-out animation can freeze interactions entirely.

Status: two independent reports (July 21 and 26), no developer response, no patch mention.

Dialogue Locks After 1.0.3

Symptom: conversations trap you with no way out, or repeat endlessly. Patch 1.0.3 fixed dialogue freezes, but on July 24, the day after, two players independently reported being trapped in a dialogue they couldn't escape. One also froze during a screen transition after passing out. A July 30 post describes conversations frequently repeating with no exit.

Escape method: spam the pause-menu or inventory button to break the loop (one player's method, unconfirmed by others).

Status: no developer reply. If it hits you, report it in the pinned "Known issues" thread with your game version β€” that's what establishes whether the 1.0.3 fix missed a case.

Wedding Event Not Triggering (Spike) β€” Fixed in 1.0.4

Fixed, and confirmed on a broken save. Patch 1.0.4 lists it twice: "Weddings should now work correctly in both Terbin and Galea" and "Spike's and Eddy's event 5 should now trigger correctly." The player who opened the original Spanish bug thread on July 21 β€” the one still blocked at ~70% Ark after finishing the game β€” came back on August 6: "They fixed it! I got married in the bugged saved game, and no problem."

So you do not need a new save. Load the file that was stuck, reach Spike as normal, and the ceremony fires.

The rest of this section is the historical picture, kept because it explains what to check if something adjacent still misbehaves.

Symptom: the marriage sequence breaks at the final step. You reach 5 hearts with Spike, give him the dating/marriage item exactly as the mayor instructs, and then nothing happens. No wedding cutscene, Spike keeps his normal daily dialogue, he never moves into the upgraded house, and the main menu already lists him as your partner. One affected player describes a half-married state where only gifting works β€” talk, joke and flirt are gone. Another player who started a completely new game reports reaching 5 hearts with Spike triggers no event at all.

How widespread: at least five players across two bug threads that appeared within hours of each other on July 27, one English and one Spanish, all with Spike. Both threads have since been deleted from the forum, so they can no longer be linked.

It looks Spike-specific. Other candidates' weddings completed normally in the same window: one player married Zoe on July 27 and she moved in, another had been married for days without issues, and later replies describe married life matter-of-factly. A July 30 post claims Eddy is affected too, but no second report has followed.

The block persisted even after one player finished the game at ~70% Ark, which ruled out "just keep playing" as a fix at the time. Patch 1.0.3 rebalanced relationship points on July 23 and all the reports post-dated it, but the developers never named a cause β€” only the fix.

Two different problems still get mistaken for this one, and neither is the patched bug:

  • Missing prerequisites. An August 1 post asked for help marrying Zoe after ten gifts and a red heart. The answer, from a player whose own Zoe wedding completed: upgrade the house first, then get the Ceremonial Ribbon from Mayor Oola's event or by buying it (they name the Terbin merchant and Alisha's father as sources). Check both before assuming a bug.
  • The dialogue-freeze bug. A July 27 post describes being unable to marry because "the game freezes whenever I talk to people." That blocks the wedding without being the wedding bug β€” see the dialogue section above.

Romance mechanics and the pre-wedding steps are in our Romance & Marriage Guide.

One cosmetic oddity from the working-wedding side (single report): the player who married Zoe says her final cutscene rendered only the player's sprite, so they stood "hugging air" while the dialogue played, and afterwards they could still romance and flirt with other candidates with nobody acknowledging the marriage. The marriage achievement unlocked normally and married life works, so this looks purely cosmetic.

Terbin Map Markers That Won't Clear ("!" and Heart Icons)

Symptom: after finishing the main quest, a purple exclamation mark and a heart icon stay on the Terbin map with no apparent quest behind them. A July 25-27 thread collected at least five players on this.

Those markers are a quest prompt, not a bug. The purple exclamation mark over Terbin is the entry point to the endgame pyramid quest line, and it only advances once you meet two conditions: house fully upgraded, and married. A few in-game days after the wedding, a cutscene with Mayor Oola triggers near the city hall and hands you two treasure maps, for Bohr and Darmstadt. That's why "upgrade the house" and "trigger Oola's cutscene" cleared the marker for earlier players β€” they were completing prerequisites.

The treasure hunt then runs through Bob the Vanadian worm, Hunter on Goddol, and Hafnir's minecart entrance, assembling the two key halves that open the pyramid. Sticking points the chain's author cleared up:

  • Darmstadt cutscene won't trigger? Explore the planet on the Speeder until it fires.
  • Bob: talk to him, don't gift him the treasure. Hand nothing over, then go see Hunter on Goddol.
  • The other treasure goes to Hafnir for a wooden carving, then to Galea, the house-upgrade NPC, for the second key half.
  • Galea ignoring you? One player holding both the carving and Hunter's key half got no reaction at all. Reopening the game didn't help. What worked: sleeping through several in-game days (visiting other planets in between), then handing the carving over at a moment when Galea wasn't busy chopping wood. Later steps can take a few in-game days to activate, so give the chain time before assuming it's broken.
  • Bob unresponsive? Patch 1.0.4 hardened the conversation logic so he can no longer be talked to while hiding in the arena β€” if the Bob step misbehaved on an older build, update before re-testing it.

On the Ark requirement, the picture is unsettled. The chain's author triggered the whole thing at roughly 87% Ark completion, so that's how the game currently behaves. But another player relayed that a developer told them the pyramid content is meant to activate at 100% Ark. If 100% is the intended design, triggering early may itself be unintended and could get patched. Treat 87% as observed behavior, not a guarantee. The developer statement is second-hand and the developers haven't posted in the thread.

What's still unexplained: one player with a fully upgraded house and a completed wedding still has both icons. So check house level and marriage, wait a few in-game days for Oola, and if the icons persist with all conditions met, that's worth filing as a report.

Ark / Museum Donation Crash

Symptom: crashes when donating at the museum/Ark, including one reviewer for whom every donation attempt crashed a fresh save.

Status: isolated reports, no direct fix named. Patch 1.0.4 does list "greater robustness when loading ark donations" β€” adjacent to this, but about loading rather than the crash itself, so update and re-test before assuming you're clear. Save before large donation sessions either way.

Loaded an EA Save? Your Ark Achievements May All Pop

Symptom: loading an Early Access save into 1.0 can instantly unlock Ark progression achievements, up to 100%, that you haven't earned. Two players confirmed it on July 17-18. One had an Ark cutscene trigger when going to check, and another reports their ship disappeared from the farm after loading (single report, not corroborated).

Impact: mostly cosmetic, with nothing gameplay-breaking confirmed. There's no supported way to relock achievements, so start 1.0 fresh if completionist integrity matters to you. Several affected players are doing exactly that. More detail in the Achievements Guide.

Controller & Steam Deck: Partial Support

  • Buttons are remappable (added in the 0.7 update), and DualShock/DualSense are formally supported.
  • Some interactions still expect a mouse. Players report reaching for mouse and keyboard for certain menus and crafting, and fishing is notably awkward without a mouse β€” a specific Steam Deck pain point.
  • The developers maintain a pinned Steam Deck compatibility thread. Check it for current status before buying primarily for Deck.

The end-of-day crash workaround above is part of the same story: controller input on specific screens is where 1.0's rough edges live.

Sprinklers Not Watering β€” Fixed in 1.0.4

Symptom, while it lasted: upgraded sprinklers didn't reliably water, and plants withered even though the soil looked watered. Orange sprinklers misbehaved generally; red ones failed when facing upward. It sat on the developers' own medium-priority known-issues list from July 21.

Fixed August 5. Patch 1.0.4: "Sprinklers: fixed watering so it works correctly, fixed the issue with multiple sprinklers and seeds being deleted after placing them." The seed-deletion half is worth noting on its own β€” placing several sprinklers around planted tiles used to destroy the seeds.

Two habits from the bugged era are still worth keeping for a few in-game days:

  • Spot-check a tile you care about the morning after rather than trusting the wet-soil visual outright. No post-patch reports contradict the fix yet, so this is caution, not a known problem.
  • Hand-water on planting day. Freshly planted seeds not counting as watered by a sprinkler on the day they go in is a separate behaviour, and 1.0.4 does not name it.

Separately, one player reports the basic sprinkler chip (found at mine level 30) can't be crafted after adding it to the fabricator β€” the recipe list just reorders (single report, not mentioned in any patch).

Not Bugs, But Asked Constantly

  • "There are no tooltips." Correct at 1.0. Crafted items like tea don't state their stamina values anywhere. Officially on the polish list.
  • "Where's the map / when are festivals?" There's no in-game map, and festival times aren't labeled on the calendar. Our Beginner Guide covers structuring your goals without one.
  • "The merchant disappeared." Wandering merchants like Bob on Vanadian move between areas by design. Two weeks without seeing one is normal exploration variance.
  • "Can I change my hairstyle after creating my character?" No. Appearance customization is creation-time only at 1.0, with change requests open on the forums.
  • "The ship's fuel cells won't activate at 100%." Working as designed, per the players who answered an August 5 thread: filling the process window to 100% yields one bar of fuel, and you can't exceed the cell capacity you've bought upgrades for. Materials sitting unprocessed aren't lost either β€” they come back if you forget to press process. No developer post in the thread.

Te'Kragh's shop menu in Farlands, with Buy and Upgrade Ship options Vendors and ship upgrades work fine at 1.0 β€” most launch friction is in input handling and missing UI affordances, not core systems. (Screenshot: JanduSoft)

FAQ

Is Farlands stable enough to buy right now? Most players complete sessions without incident, and the worst blocker (blacksmith) is fixed. But the end-of-day crash is real for an unlucky subset, and the developers themselves frame the coming months as bug-fixing time. Watch the patch notes for two or three updates first if a rough launch week bothers you.

How fast do the developers patch? Mixed record, trending positive. The blacksmith fix took weeks longer than the community wanted but it shipped before 1.0, the team runs pinned known-issues and reporting threads, and their launch announcement commits the next couple of months to fixes and feedback.

My issue isn't listed. Report it in the pinned "Known issues and how to report them" thread on the Steam forums. The developers direct all reports there.