Grounded is at its best when chaos hits the backyard and everyone scrambles to survive the same threat at the same time. A spider aggro pull goes wrong, someone whiffs their parry window, and suddenly the base defense you all built together is on the line. Shared Worlds exist to make sure those moments don’t live and die with a single host’s save file.
Core Concept: One World, Multiple Hosts
A Shared World in Grounded is a persistent save that lives independently of any single player’s device. Instead of the world being locked to whoever originally hosted the session, the save is uploaded and stored so that approved players can launch it themselves. If one person logs off mid-session, the world doesn’t vanish with them.
This fundamentally changes co-op flow. Anyone with permission can boot the world, continue progression, and keep the backyard evolving without waiting for a specific friend to be online.
Purpose: Solving the “Host Problem”
Standard multiplayer saves in Grounded are host-dependent. The host owns the world, controls when it’s online, and holds all progression data. If they’re busy, the entire group is hard-stopped, no matter how geared or prepared everyone else is.
Shared Worlds exist to remove that bottleneck. They’re designed for friend groups who play asynchronously, where base building, farming, and story progression shouldn’t be gated by one schedule. It’s Grounded acknowledging that co-op survival lives or dies by accessibility.
How Shared Worlds Are Created
A Shared World is created by converting an existing save or starting fresh with Shared World enabled. The creator becomes the initial owner and controls who gets access. Once shared, the world syncs to the cloud and becomes selectable for other authorized players from their own menus.
Importantly, this isn’t a copy. Everyone is interacting with the same persistent instance, not parallel versions split by host sessions.
Ownership, Permissions, and Control
While multiple players can host a Shared World, ownership still matters. The owner decides who can access the world and can revoke permissions at any time. This prevents griefing, accidental deletions, or someone rolling back progress without group consent.
Other players function as secondary hosts. They can load the world, save progress, and advance the game, but they don’t override ownership-level controls unless explicitly granted.
Progression Syncing and Save Behavior
All progression in a Shared World is global. Base construction, story objectives, BURG.L chip unlocks, gear crafting, and world changes are saved the moment the session ends. There’s no split loot tables or desynced quest states to worry about.
Character inventories and mutations are also preserved per player. You’re not logging into a generic avatar; you’re continuing your own build inside a shared environment.
How This Differs From Standard Saves
Standard saves are local-first and host-locked. Only the host can advance the world, and if that save is lost or corrupted, the entire group loses everything. Shared Worlds remove that single point of failure by decentralizing access.
The trade-off is control. Shared Worlds prioritize group continuity over individual authority, which means trust matters. You’re giving others the power to affect a world you care about, for better or worse.
Limitations and Smart Use Cases
Shared Worlds still require someone to be actively hosting; they aren’t always-on servers. If no authorized player is online, the world is offline. Mods, if used, must be consistent across hosts to avoid conflicts.
The system shines for long-term co-op campaigns, rotating play schedules, and groups pushing endgame content together. It’s less ideal for solo-focused worlds or players who want absolute control over every save state.
Creating a Shared World: Host Requirements, Setup Options, and Initial Ownership Rules
Once you understand how Shared Worlds shift control away from a single host, the next question is obvious: how do you actually make one without risking your progress? Grounded keeps the setup straightforward, but there are some critical decisions baked into creation that affect long-term control, access, and stability.
This isn’t just a toggle you flip mid-session without consequences. Creating a Shared World defines who owns it, who can host it later, and how resilient that save will be over dozens of co-op hours.
Who Can Create a Shared World
Any player can create a Shared World, but the creator automatically becomes the owner. Ownership is permanent unless explicitly transferred, and it carries more weight than most players realize early on.
The owner is the only player who can manage access permissions, remove players, or delete the Shared World entirely. Even if everyone else has hosted the world dozens of times, the owner remains the final authority.
Because of that, the ideal owner is the most consistent or responsible player in the group. If the owner disappears, stops playing, or deletes the world, there’s no recovery option for the rest of the team.
Creating a Shared World From a New Save
When starting fresh, Shared World creation happens during world setup. After choosing difficulty, game settings, and world options, you’ll be prompted to mark the save as a Shared World.
From that moment forward, the world is no longer host-locked. Once other players are invited and granted access, they can host the world independently, progressing the same persistent instance.
This is the cleanest way to use the system. No legacy data, no conversion risks, and no confusion about who owns what when the campaign begins.
Converting an Existing World Into a Shared World
Grounded also allows you to convert an existing standard save into a Shared World, but this should be done carefully. The current host of that save becomes the owner at the moment of conversion.
All existing progress carries over intact, including bases, items, story progression, and player inventories. What changes is access: once shared, invited players can host and advance that world without the original host being present.
Before converting, groups should agree on ownership. If the wrong player converts the save, there’s no way to retroactively change who owns it without transferring ownership manually later.
Inviting Players and Granting Access
After creation, the owner must explicitly invite players to the Shared World. Being a friend on Xbox Live or Steam isn’t enough; access is tied to permissions, not your friends list.
Once invited, players gain hosting rights by default. That means they can load the world, play solo or with others, and save progress just like the owner.
Access can be revoked at any time. If someone is prone to risky experimentation, base redesigns without consensus, or accidental item loss, the owner can remove them without affecting the world itself.
Initial Ownership Rules and What They Mean Long-Term
Ownership defines control, not playtime. A player who hosts 90 percent of sessions still doesn’t gain authority unless the owner transfers it.
This matters for conflict resolution and world safety. Only the owner can delete the Shared World, which prevents a bad night of decisions from wiping hundreds of hours of progress.
Best practice is simple: treat ownership like a guild leader role. Choose carefully, communicate expectations early, and remember that Shared Worlds are about continuity, not convenience.
How Progression Syncs: Bases, Story Progress, Inventory, and World State Explained
Once ownership and access are locked in, the most important question becomes simple: what actually syncs when multiple people are advancing the same Shared World? Grounded’s system is surprisingly robust, but it follows strict rules that every co-op group needs to understand to avoid lost items, duplicated effort, or accidental progression skips.
This isn’t a loose “host-based” save like traditional co-op. Shared Worlds track the backyard itself as the source of truth, not the player who last logged out.
Base Building and World Changes Are Fully Persistent
All construction is global. Every wall, zipline, mushroom brick, and relocated dandelion tuft saves directly to the Shared World the moment the game autosaves or a player sleeps.
If one player finishes a base expansion while playing solo, everyone else will see it exactly as it was left. There’s no merge process, no version conflict, and no rollback unless the owner manually intervenes with older backups.
The same applies to destruction. If someone dismantles a staircase or lures a wolf spider through your storage room, that damage is permanent and synced for all players.
Story Progress Is Shared Across the Entire Group
Main story milestones are global flags. If one player completes a BURG.L quest, activates a lab, or progresses the campaign while hosting alone, the entire Shared World advances.
This means late-joining players can log in and find key story beats already completed. Labs may be cleared, doors unlocked, and critical encounters already resolved.
For groups that care about narrative pacing, this is huge. Communication matters, because the game does not gate story progress behind full-party presence.
Player Inventory Is Individual, Not Shared
Inventories are tied to characters, not the world. Your armor, weapons, trinkets, mutations, and carried items stay with you no matter who hosts.
If you log out holding the group’s only Tier III hammer, it logs out with you. The world doesn’t duplicate it, and nobody else can access it unless you’re online or you stored it in a chest.
Backpacks follow standard Grounded rules. If you die, your backpack remains in the world, visible and lootable by others until you reclaim it.
Storage Containers Are Fully Shared
Chests, pallets, grinders, and all other storage structures belong to the world itself. Anyone with access can deposit or withdraw items at any time.
There are no permissions or personal locks. If it’s in a chest, it’s fair game, for better or worse.
Most experienced groups solve this socially, not mechanically. Labeling storage rooms, assigning crafting roles, and agreeing on “do not touch” resources prevents more drama than any system ever could.
Crafting Unlocks and Tech Progress Sync Automatically
Analysis unlocks, BURG.L shop purchases, and crafting recipes apply globally. Once something is unlocked, everyone benefits instantly.
If one player spends Raw Science to unlock advanced upgrades, the entire group gains access to those crafting paths. There’s no need to rebuy or re-scan items individually.
This makes specialization efficient, but it also means careless spending affects everyone. Treat Raw Science like a shared currency, because functionally, it is.
Creature State, Boss Kills, and World Events
Enemy deaths, boss completions, and major world events persist. Kill a broodmother, and she stays dead until her respawn conditions are met.
Creature aggro and positioning reset normally when players leave the area, but structural changes and defeated encounters remain resolved. You can’t farm the same boss repeatedly just by swapping hosts.
Time of day, weather, and world conditions also carry forward. Logging in mid-night because someone saved at midnight is part of the Shared World experience.
Player Location and Save Behavior
Each player logs back in where they last saved, not at a shared spawn point. If you logged out deep in the haze, you’ll log back in there, even if no one else is online.
This can be dangerous if the world advanced without you. Bases may have moved, paths may be blocked, and enemies may have respawned nearby.
Smart groups log out in safe locations, especially when someone else is likely to host the next session.
Difficulty Settings and World Rules Are Locked
Difficulty and custom game settings are fixed to the Shared World and controlled by the owner. Other players cannot change them when hosting.
This prevents someone from quietly dropping difficulty for a farming run or toggling survival mechanics without group consent.
If your group wants to adjust rules mid-campaign, that conversation has to happen with the owner, not the host of the night.
Shared Worlds don’t just let everyone play anytime. They turn Grounded into a single, living backyard where every decision, good or bad, becomes part of the same ongoing survival story.
Player Access and Permissions: Who Can Launch the World and What Control They Have
All of those persistent systems only work because Shared Worlds in Grounded are built around strict access rules. Who launches the world, who can invite others, and who has authority over settings isn’t random. It’s a hierarchy, and understanding it prevents lost progress, locked-out sessions, and the classic “who actually owns this save?” disaster.
The World Owner: Absolute Authority
Every Shared World has a single owner, defined at creation. That player holds permanent control over world rules, difficulty, and long-term configuration.
Only the owner can change difficulty, toggle custom game options, or remove the world from Shared status. Even if someone else hosts a session, they’re operating within boundaries the owner already locked in.
If the owner deletes the world or revokes sharing, the Shared World is gone. There’s no backup copy for other players unless they made a manual standard save beforehand.
Hosts vs. Guests: Who Can Actually Launch the World
Any player the owner shares the world with can launch it, even if the owner is offline. That’s the core advantage of Shared Worlds and the reason co-op schedules stop falling apart.
However, launching the world doesn’t grant ownership privileges. Hosts can start sessions, save progress, and invite other shared players, but they cannot alter core world settings.
Think of hosts as session drivers, not designers. They move the car forward, but they don’t get to rebuild the engine.
What Hosts Can and Can’t Control
Hosts fully control moment-to-moment gameplay. They can save the world, log out whenever they want, and determine when a session ends.
What they cannot do is roll back progress, change difficulty, enable creative-style toggles, or undo permanent decisions like boss kills or Raw Science spending. Once a host saves, those changes are locked into the Shared World for everyone.
This means trust matters. Letting someone host is effectively letting them write the next chapter of your shared survival story.
Guest Players and Join Permissions
Guests are players who join a session but don’t have the world shared directly with them. They can play normally during that session but can’t launch the world on their own later.
Their progression, inventory, and location still save correctly, but access is session-dependent. If they’re not invited back, they’re effectively locked out of that Shared World.
For long-term group members, direct sharing is essential. Guests are best used for drop-in help, boss fights, or teaching new players the ropes.
Best Practices for Group Control and Safety
Before starting a Shared World, agree on who should own it. The owner should be the most reliable player, not necessarily the most skilled.
Limit sharing to players you trust to make permanent decisions. One rushed host can burn Raw Science, trigger a boss fight early, or save after a disastrous base wipe.
If your group rotates hosts often, communicate before big actions. Shared Worlds don’t forgive impulsive saves, and there’s no quick reload when someone presses the wrong button.
Ownership, Hosting, and Offline Play: How Shared Worlds Persist Without the Original Host
This is where Grounded’s Shared Worlds quietly solve one of co-op survival’s biggest pain points: what happens when the original host isn’t around. After locking down who can host and what control actually means, the real magic is how the world itself stays alive even when its creator is offline.
Shared Worlds aren’t tied to a single player’s console or schedule. Instead, they exist as a persistent save that multiple trusted players can launch, progress, and save independently, without breaking progression or desyncing character data.
World Ownership vs. Who Can Actually Play
Ownership in Grounded is permanent and exclusive. The player who creates the Shared World is its owner, and that status never changes unless the world is deleted entirely.
That ownership doesn’t gate access, though. Any player the owner shares the world with can host it at any time, even if the owner hasn’t logged in for weeks. This is the core difference between Shared Worlds and traditional host-based saves.
The owner acts more like an administrator than an active gatekeeper. They define who has long-term access, but they don’t need to be present for the world to function.
How Hosting Works When the Owner Is Offline
When a shared player launches the world, they become the active host for that session. The game pulls the latest cloud-synced version of the world and spins it up exactly where the last host saved.
There’s no “secondary copy” or split timeline happening behind the scenes. Every save writes back to the same Shared World, meaning progression, base changes, and story milestones are always unified.
As long as someone with direct access is online, the backyard keeps moving forward. No waiting, no asking for save files, and no resetting days because the wrong person hosted.
Offline Progression and Save Persistence
Offline play is where Shared Worlds truly flex. A shared player can jump in solo, farm resources, rebuild defenses, or prep for a boss fight, then save and log out without anyone else present.
Those changes are permanent the moment the save completes. When other players log in later, they load into that updated world state, complete with new structures, upgraded gear, and any irreversible choices that were made.
This makes Shared Worlds incredibly powerful, but also dangerous. Offline progress is still real progress, and there’s no safety net if someone makes a call the group wasn’t ready for.
What Happens If the Owner Disappears
If the owner stops playing entirely, the Shared World doesn’t collapse. As long as at least one other player has direct access, the world remains fully playable and hostable.
The only thing that’s lost is the ability to share the world with new players. Since only the owner can grant access, the player list is effectively frozen once they’re gone.
For established groups, this usually isn’t an issue. For expanding friend groups, it’s a reminder that ownership is a long-term commitment, not just a formality during creation.
Why Shared Worlds Feel So Stable Compared to Traditional Co-op
Traditional co-op saves live and die by the host’s availability. Miss a night, lose momentum, and eventually the group drifts apart.
Shared Worlds remove that dependency entirely. Progress doesn’t stall, bases don’t sit idle, and schedules stop dictating whether the backyard survives another day.
It’s a system built around trust, persistence, and respect for player time. When used correctly, it turns Grounded from a “when can everyone play?” game into a living world that’s always ready when you are.
Limits and Constraints: Player Caps, Save Conflicts, Mods, and Version Compatibility
Shared Worlds feel almost frictionless once they’re running, but they’re not limitless. Understanding where the system draws hard lines is what keeps a long-running backyard from imploding due to technical issues or mismatched expectations.
This is where Grounded stops being a cozy co-op survival game and starts behaving like a persistent service. Player limits, save rules, and version control all matter, especially once dozens of in-game days are on the line.
Player Caps and Session Limits
Grounded Shared Worlds cap out at four concurrent players per session, including the host. That limit is absolute, regardless of platform, progression, or hardware strength.
You can grant direct access to more than four players total, but only four can be active in the world at the same time. Anyone extra has to wait until a slot opens, just like a traditional co-op lobby.
This cap also affects combat balance. Enemy aggro scaling, DPS checks during boss fights, and raid intensity all assume a maximum four-player squad, so the system stays mechanically stable even in late-game chaos.
Save Conflicts and World State Authority
Shared Worlds avoid most traditional save conflicts by enforcing a single authoritative world state. Only one instance of the world can be live at any given time, meaning two players can’t host separate versions in parallel.
If someone is already hosting the Shared World, no one else can load it until that session ends. This hard lock prevents split timelines, duplicated resources, or RNG desyncs that would otherwise corrupt progression.
It also means communication matters. Logging in solo and triggering a base raid, spending shared upgrade materials, or flipping major world switches is permanent the moment the save completes.
Mods and Shared World Compatibility
Mods are where Shared Worlds get risky fast. Grounded’s Shared Worlds are designed around a vanilla ruleset, and mods must be installed and matched across all players to avoid crashes or failed loads.
If a Shared World was saved with mods enabled, every player hosting or joining that world needs the same mod set and load order. Missing or mismatched mods can prevent the world from loading entirely.
For long-term shared saves, most groups are better off staying unmodded. Stability beats novelty when hundreds of hours of base-building and gear progression are on the line.
Version Mismatch and Platform Syncing
All players accessing a Shared World must be on the same game version. Even minor patches can temporarily block access until everyone updates.
This applies across platforms as well. PC, Xbox, and cloud players can share worlds seamlessly, but only if they’re fully synced to the latest build.
If one player delays an update, they’re effectively locked out until they patch. The world itself remains safe, but progress pauses for that individual.
Ownership Constraints and Access Control
While Shared Worlds feel communal, ownership still carries exclusive power. Only the original owner can grant or revoke direct access to the world.
Other players can host, progress, and save freely, but they cannot add new members or transfer ownership. That control never changes hands.
For groups planning multi-month playthroughs, choosing the owner isn’t just a formality. It’s a trust decision that defines who ultimately controls the backyard’s future.
Converting Existing Saves into Shared Worlds (and When You Shouldn’t)
If your group started in a standard single-player or multiplayer save, Grounded does let you convert that world into a Shared World. This is how most long-running backyards make the jump once scheduling becomes a nightmare.
But this isn’t a cosmetic toggle. Converting a save fundamentally changes how ownership, access, and risk work going forward.
How the Conversion Process Works
From the save select screen, the original owner can choose an existing world and convert it into a Shared World. Once confirmed, that save is uploaded to Xbox cloud storage and flagged for shared access.
After conversion, the world no longer lives exclusively on the owner’s local system. Any authorized player can now host, save, and progress the world independently.
The process is one-way. There is no rollback to a traditional save once the conversion is complete.
What Carries Over (and What Doesn’t)
All world data transfers cleanly. Base builds, creature spawns, story progression, molar upgrades, and unlocked crafting recipes remain exactly as they were.
Player inventories, mutations, and gear also persist without changes. No DPS losses, no reset aggro tables, no stealth flag weirdness.
What does change is save authority. Once shared, you’re trusting every authorized player with the entire timeline of that world.
When Converting Is the Right Call
Shared Worlds shine when your group can’t reliably play together. If one player farms quartzite, another pushes story labs, and a third just loves base design, Shared Worlds let all that progress stack.
They’re also ideal for long-term survival runs where burnout is a risk. Being able to log in solo, repair walls after a raid, or prep smoothies before a boss fight keeps momentum alive.
If your group already communicates well and respects shared resources, conversion removes friction instead of adding it.
When You Absolutely Shouldn’t Convert
If your save uses experimental mods, custom difficulty tweaks, or niche rule changes, converting is a gamble. One mismatched setup can brick access until everyone aligns perfectly.
You should also avoid converting if one player tends to impulse-spend upgrades, trigger MIX.R defenses unannounced, or push story flags solo. Shared Worlds don’t have undo buttons.
Finally, early-game saves often benefit from staying traditional. Before core roles, base locations, and progression plans are locked in, shared access can create more chaos than convenience.
Best Practices Before You Commit
Make a manual backup of the original save before converting. That snapshot is your only safety net if something goes sideways.
Agree on ground rules. Who’s allowed to advance story beats, start base raids, or relocate critical infrastructure should be decided up front.
Once converted, treat the world like a living server, not a personal playground. The moment the save completes, every choice becomes permanent for everyone involved.
Best Practices for Co-op Groups: Avoiding Progress Loss, Managing Resources, and Communication Tips
Once your world is shared, the game stops treating it like a personal save and starts treating it like a server. That means every action has ripple effects, whether you’re farming lint solo or pulling aggro from a Black Ox Beetle at midnight. These best practices are about keeping momentum without stepping on each other’s progress.
Respect Save Authority and Session Discipline
In a Shared World, whoever is logged in effectively controls the timeline while they’re playing. Quitting mid-raid, force-closing during a wipe, or dashboarding to dodge consequences can corrupt expectations, even if the save technically survives.
Set a rule that major events happen during stable sessions. Boss fights, MIX.R defenses, and lab pushes should only be triggered when players can finish the job or clearly communicate a handoff.
Lock Down Story Progression
Story beats in Grounded aren’t cosmetic. Unlocking labs, flipping BURG.L chips, or triggering endgame sequences permanently changes the world state for everyone.
Designate who’s allowed to advance the main story, or require a group vote before touching critical objectives. This avoids the classic co-op problem where one player logs in solo and skips three hours of shared discovery.
Create a Resource Economy, Not a Free-for-All
Shared storage is where most co-op worlds implode. Quartzite, marble, lint, and broodmother chunks are progression bottlenecks, not casual crafting mats.
Use labeled chests and agreed categories. One for upgrades, one for base repairs, one for personal projects. If someone needs to pull from progression stock, they announce it first, no exceptions.
Set Clear Rules for Gear, Mutations, and Loadouts
Player inventories persist, but crafting decisions echo. Upgrading a Tier III weapon consumes finite resources and shifts team DPS potential.
Agree on combat roles early. Who’s running tank with aggro control, who’s building ranged DPS, and who’s leaning support or utility mutations. This prevents overlapping builds and wasted upgrades that slow the entire group.
Base Building and Relocation Needs Consensus
Relocating a base or redesigning defenses isn’t just cosmetic busywork. It affects spawn safety, raid vectors, and daily traversal routes.
No major construction changes without a heads-up. If someone wants to experiment with a new outpost or zipline hub, it should supplement the main base, not overwrite it during off-hours.
Define Offline Play Boundaries
Shared Worlds thrive on asynchronous play, but only if boundaries are clear. Farming, repairing, cooking, and prepping smoothies are usually safe solo activities.
Advancing story flags, starting raids, or experimenting with high-risk fights offline is where progress loss happens. If the activity can’t be safely rolled back, it shouldn’t be done without the group knowing.
Communicate Like a Raid Team, Not a Group Chat
You don’t need constant chatter, but you do need signal over noise. A simple message like “used 6 sturdy marble for spear upgrade” prevents confusion and resentment later.
Use pinned notes, Discord channels, or even in-game signs near storage to track decisions. Clear communication keeps Shared Worlds feeling collaborative instead of chaotic.
Always Maintain a Backup Mindset
Shared Worlds don’t offer manual version control. If something goes wrong, there’s no rewind button.
Before major milestones, agree to pause and ensure the world syncs cleanly. Treat big moments like patch days, not casual logins, and you’ll avoid the kind of progress loss that ends co-op runs for good.
Common Shared World Problems and Fixes: Desyncs, Missing Progress, and Access Issues
Even with solid rules and communication, Shared Worlds in Grounded can still throw curveballs. Most issues don’t come from bugs alone, but from how the system handles ownership, syncing, and offline progression.
Understanding what’s actually happening under the hood is the difference between a quick fix and a co-op run that quietly collapses.
Desyncs: When the World Doesn’t Match for Everyone
Desyncs usually show up as rubberbanding, missing structures, or enemies behaving differently for each player. In Shared Worlds, the active host is always the authority, meaning their connection stability dictates how clean the session feels.
If things start feeling off, have everyone log out and let the world owner rehost. This forces a fresh sync from the cloud save and resolves most phantom issues without risking progress.
Avoid hot-swapping hosts mid-session. While Grounded supports it, repeated transfers increase the odds of state mismatches, especially during raids or scripted events.
Missing Progress: Why Builds, Quests, or Items Vanish
This is the big one, and it almost always ties back to unsynced saves. Shared Worlds only commit progress when the session ends cleanly and the save uploads successfully.
If someone force-quits, crashes, or loses connection during a major action, that progress may never lock in. Always return to the menu properly, especially after base upgrades, boss fights, or story triggers.
As a rule, avoid doing high-impact activities during unstable network conditions. RNG loot can be farmed again. Lost quest flags or base edits hurt far more.
Access Issues: “Why Can’t I Load Our World?”
Shared Worlds are tied to the creator’s save permissions. If a player can’t access the world, it’s usually because the owner hasn’t explicitly shared it with them or their platform account isn’t syncing properly.
Double-check the Shared World settings from the main menu, not in-session. Players must be added there, and changes don’t always propagate instantly.
If access still fails, have the owner load the world solo once, exit cleanly, then re-invite players. That refresh alone fixes most access lockouts without deleting or recreating the save.
Platform Sync and Cross-Play Pitfalls
Grounded’s cross-play is solid, but cloud sync delays can happen between platforms. Xbox and PC players may see different world states if one platform hasn’t finished uploading.
Before a long session, give the world a minute to fully sync after loading. Rushing straight into combat or building increases the risk of partial state saves.
If something looks wrong, trust the save timestamp, not your memory. The most recent clean save is the authoritative version, even if it means replaying a few minutes.
When to Cut Losses and Stabilize the World
If problems keep stacking, stop playing. Continuing in a broken state compounds issues and makes recovery harder.
Have the owner load the latest stable save, confirm structures and story flags, then re-open the session. Think of it like resetting a raid after a bad pull instead of trying to brute-force a scuffed run.
Grounded’s Shared Worlds are powerful, but they reward discipline. Treat the save with the same care you’d give a hardcore survival character, and it will carry your group from backyard chaos to endgame dominance without losing a step.