Grounded 2 Rot and Ruin: what to check before returning

Grounded 2’s October 20 Rot and Ruin notes describe new content and a smaller PC installation. Before returning, check your installed build: the announcement still uses future-facing language rather than confirming a precise rollout time for every platform.

What Rot and Ruin adds

The described additions include the Woodpile, the Centipede boss and the Potato Beetle Buggy. Painting uses the Splotcher; Bismuth and the Yoking Press let you raise equipment tiers. These are useful signposts for deciding what you want to try first.

Pick a reason to return before organising a long session. If exploration is your priority, make discovering the new area your goal rather than promising the group a boss clear. If you prefer building, plan a small redesign before committing to a whole base. If progression matters most, inspect the upgrade options before spending resources. That gives each kind of player a manageable starting point without pretending every addition must be completed immediately.

The smaller installation needs context

Obsidian reports a 51% PC size reduction, from 37GB to 18GB; the console reduction is only 200–300MB. Steam still specifies 40GB of available storage. Treat the first figure as an installed-size claim and the second as the store’s published requirement, not as interchangeable measurements.

The practical answer is to let your launcher show what this installation actually needs. Do not calculate the download by subtracting the two installation sizes, and do not reserve exactly the smaller amount of free space. Check the pending download and any disk-space warning before removing other games. If bandwidth is limited, start this check before your friends assemble rather than assuming a smaller final installation means a small transfer.

Storage also tells you nothing by itself about the frame rate your PC can sustain. Compare your hardware with the current store requirements and keep your existing settings as a baseline. An improvement worth trusting is one you can repeat in the same area with the same settings, not a comparison between a quiet scene today and a crowded scene months ago.

Prepare your return in five steps

On PS5, the store requires PlayStation Plus for online play and lists up to four online players. If you are adding a friend on that platform, check their access before choosing a time. The listing also warns that progress may be affected when the game reaches 1.0; that is a future-transition warning, not confirmation that this update wipes your world.

For groups returning to several co-op games, our PEAK crossplay and cross-save explainer covers another common planning mistake: assuming that playing together automatically means progress transfers. Check each game’s own rules rather than carrying an expectation from one title into another.

Public testing is a separate decision

Obsidian describes the Public Test Build as a higher-risk branch for feedback, not simply another name for Early Access. Its instructions recommend starting a new game because test content can affect previous saves. On Steam, the documented way to leave the test branch is through the game’s Properties and Betas settings, choosing the option to opt out.

Do not join testing solely because you see an update article. First establish what is available in your normal installation. Choose a public test only if you actively want to help test unfinished changes and accept the extra risk. For a group with limited time, keeping everyone on the intended branch is a better first step than asking each person to troubleshoot a different setup.

What still needs checking

The dated notes also say Rot and Ruin arrives “this fall.” Confirm availability in your launcher instead of treating the publication date as a regional unlock schedule.

The official issue tracker distinguishes problems under investigation, fixes intended for a future patch and fixes on the live game. Read the status as well as the issue title. A future-fix label is not proof that your installed build contains the fix. Search for your specific symptom before assuming a broad performance or stability statement resolves it.

This explainer is based on official information, not hands-on testing. It cannot establish performance on your hardware, the difficulty of the new encounters or whether a particular older save will behave correctly. If a past technical problem is the reason you stopped playing, make reproducing that problem your first test. If you are considering a first purchase, judge the currently available game rather than buying on the assumption that future updates will solve your objections.