Feed and Grow: Fish not working usually comes down to one of five things: a corrupted or partial game install, a missing or outdated Visual C++ runtime, blocked network ports for multiplayer, an antivirus quarantine of the game executable, or a GPU driver that no longer matches the Unity engine build the game ships with. The game is a small indie title built on Unity and distributed through Steam, so nearly every failure traces back to client-side files, permissions, or runtime libraries rather than server outages. Below is a mechanism-level breakdown of each failure mode, how to confirm it, and what actually fixes it.
How the Unity runtime chain fails at launch
Feed and Grow: Fish runs on Unity, which means the executable is a thin launcher that hands off to a stack of managed and native libraries. The player executable loads Mono or IL2CPP assemblies, then the UnityPlayer DLL, then your GPU driver's Vulkan or Direct3D interface. If any link is missing or version-mismatched, the process exits before a window appears, and Steam shows nothing.
The most common break is the Microsoft Visual C++ Redistributable. Unity builds compiled with certain toolchains require a specific redistributable year (2015, 2017, or 2019, depending on the build). If Windows has an older or partially registered version, the game crashes at the first native call with no dialog. This is why "verify integrity of game files" sometimes does nothing: Steam restores the game files but cannot repair a system-level redistributable.
A second common break is the save directory. Unity games write to %USERPROFILE%\AppData\LocalLow by default. If that path is redirected by OneDrive, blocked by Controlled Folder Access, or owned by a different Windows account after a migration, the game either hangs on the loading screen or crashes when it first tries to write. The symptom looks like a hang, but the cause is a permissions denial on a folder the game assumes it owns.
Plain language: the game is a chain of dependencies, and it fails silently at whichever link is broken.
What the failure modes look like in numbers
Different failures produce distinct signatures. Crashes on launch with no window cluster in the first 2–5 seconds and almost always map to a runtime or redistributable problem. Crashes after the splash screen but before the main menu cluster around 5–15 seconds and usually map to a GPU driver or shader compilation issue. Multiplayer disconnects typically occur within 30–90 seconds of joining a lobby and point to network address translation or firewall problems.
Steam's verify process re-downloads only files that fail a hash check against the depot manifest. It does not touch the registry, the redistributables, or your save folder. That is why verification fixes maybe half of install-related failures and almost none of the runtime or network ones.
Unity's crash handler writes a Player.log and a crash dump to %USERPROFILE%\AppData\LocalLow<Company><Game>. The last 20–40 lines of Player.log often name the exact missing DLL or the exception that killed the process. Reading that file converts a vague "not working" into a specific, fixable fault.
Launch and multiplayer failure timeline
| Elapsed time | Symptom | Most likely cause | First check |
|---|---|---|---|
| 0–3 seconds | Nothing happens, Steam shows "Running" then stops | Missing VC++ redistributable or blocked executable | Player.log tail, antivirus quarantine |
| 3–10 seconds | Splash appears, then closes | GPU driver mismatch or shader cache corruption | Driver version vs. GPU model |
| 10–30 seconds | Main menu loads, then hangs on "New Game" | Save folder permissions or disk space | AppData\LocalLow ownership, free space |
| 30–90 seconds | Loads fine, disconnects in multiplayer | NAT, firewall, or port blocking | Router UPnP status, Windows Firewall rules |
| Minutes to hours | Playable but stutters or drops frames | VRAM pressure or thermal throttling | GPU memory usage, temperatures |
Multiplayer failure is a network path problem, not a server problem
Feed and Grow: Fish multiplayer depends on peer-to-peer or relayed connections rather than a large dedicated server farm. When lobbies fail to appear or players drop, the bottleneck is almost always the path between two clients, not the game's central infrastructure.
The mechanism is address translation. Your router assigns your machine a private address and rewrites outbound packets. For a peer connection to form, either UPnP must open the right port automatically, or the game must use a relay. If UPnP is disabled on the router, and the relay is slow or blocked by a strict firewall profile, the lobby handshake times out. The game then reports a generic connection failure that looks like the game is broken.
Windows Firewall adds a second layer. On first launch, Windows prompts to allow the game through the firewall. If that prompt was dismissed or denied, the rule is created as a block, and it persists silently across updates. Checking the inbound and outbound rules for the game executable resolves a large share of "multiplayer doesn't work" reports.
A counterintuitive detail: a fast internet connection does not guarantee working multiplayer. A symmetric gigabit line behind strict carrier-grade NAT can fail where a slower line behind a UPnP-enabled router succeeds. The constraint is reachability, not bandwidth.
Save corruption, antivirus quarantine, and other edge cases
Save corruption is the failure mode that looks most like a game bug. Unity writes save data in a temporary file and then renames it. If the process is killed mid-write, or if the drive runs out of space during the rename, the save file is left truncated. The game then either refuses to load it or loads an empty world with no error message.
Antivirus quarantine is the second most underdiagnosed cause. Small indie executables are sometimes flagged by heuristic scanners because they lack a signed reputation history. When the executable is quarantined, Steam still shows the game as installed, and launching it produces either nothing or a generic error. The fix is to restore the file from quarantine and add an exclusion for the game folder, not to reinstall repeatedly.
Red-flag warnings worth checking before anything else:
The game folder or the AppData save path is inside a OneDrive or cloud-synced directory that is actively syncing. Windows Controlled Folder Access is enabled and has no exception for the game. The system drive has less than 10 percent free space, which breaks temporary file writes. The GPU driver was updated within the last 48 hours and the game worked before that update. A third-party overlay (Discord, MSI Afterburner, RTSS) is hooking the process and crashing it at launch.
Common misconceptions that waste troubleshooting time
The first misconception is that reinstalling fixes everything. Reinstalling restores the game files but leaves the redistributable, save folder, firewall rules, and registry entries untouched. If the fault is in any of those, a clean reinstall changes nothing, and players conclude the game is permanently broken.
The second misconception is that a Steam server outage explains a failure. Feed and Grow: Fish is small enough that its matchmaking infrastructure rarely goes down for long, and a true outage would affect every player, not just one. If the game launches for others and not for you, the fault is local.
The third misconception is that performance stutter means the game is "not optimized." Stutter in a Unity title usually comes from VRAM exhaustion or shader compilation, both of which are hardware- and driver-dependent. A GPU with 4 GB of VRAM running at high texture settings will stutter where an 8 GB card will not, on identical game code.
Plain language: most "broken game" reports are environment problems wearing a game-problem costume.
Practical diagnostic and repair sequence
Work through these in order. Each step isolates one layer, so you stop guessing after the first confirmed fault.
Read the log first. Open %USERPROFILE%\AppData\LocalLow and find the game's company folder. Open Player.log and read the last 30 lines. A named missing DLL or an "access denied" line points straight to the cause. Repair the runtime. Install the latest Microsoft Visual C++ Redistributable for both x64 and x86, then reboot. This resolves the most common launch-with-no-window failure. Verify and recheck. Run Steam's verify integrity, then launch once with overlays disabled. If it now works, re-enable overlays one at a time to find the culprit. Check quarantine and firewall. Confirm the executable is not quarantined, then confirm the firewall has allow rules for both private and public profiles. Delete any block rules. Test the save path. Move or rename the save folder to force the game to create a fresh one. If a new save works, the old save is corrupted and the fault is confirmed. Isolate multiplayer. Test on a different network (mobile hotspot) to determine whether the fault is the router or the client. If the hotspot works, the home router's UPnP or NAT is the problem.
If none of these resolve the failure, capture the Player.log and the crash dump and post them to the game's official community hub. A log with a named exception is diagnosable; "it doesn't work" is not.
What cannot be fixed from the player side
Some failures are outside your control. If the game's build has a genuine engine-level bug triggered by a specific GPU architecture or Windows build, no amount of local troubleshooting will resolve it until the developer patches it. Small indie teams ship updates infrequently, so a confirmed engine bug can persist for weeks or months.
Server-side matchmaking outages and relay failures also fall outside the player's reach. These are usually brief, but during a spike in player count they can last hours. In those cases the correct action is to wait and check the community hub for confirmation, not to reinstall.
Finally, hardware incompatibilities at the driver level, such as a GPU whose vendor has dropped support for the Direct3D feature level the game requires, cannot be worked around locally beyond lowering settings or rolling back to an older driver. That is a limitation of the platform, not a defect you can repair.
This article is general educational information about software troubleshooting, not a guarantee of a fix or a substitute for the developer's official support. Outcomes depend on your specific hardware, network, and Windows configuration. For persistent failures, consult the game's official support channels or a qualified local technician.