The Short Answer
Every co-op survival server, whether it is a three-person Valheim world or a full Rust clan, runs on a social contract that nobody ever writes down. It is the reason some servers last for months and become the best gaming memories of your year, and others implode in a week over a stolen stack of iron. The rules are not in any tutorial, but they are remarkably consistent across games: respect the shared base, contribute before you consume, do not touch what is not yours, and communicate before you do anything that affects everyone else. Get those right and a survival server becomes a second home. Get them wrong and you become the reason the group stops logging in. This is a HostedGG culture piece about the etiquette that keeps a shared world alive.
Rule One: The Base Belongs to Everyone, So Act Like It
The single fastest way to kill a co-op server is to treat the shared base like your personal property. In most survival games, the main base is a commons. Everyone built it, everyone stores loot in it, and everyone depends on it. That creates an obligation most new players miss: do not reorganize, deconstruct, or "improve" the group's base without asking.
You may be right that the storage would be better sorted, the walls better placed, the farm better laid out. Do it anyway without a word and you have just erased someone else's work and muscle memory. In Valheim, moving a portal breaks someone's travel network. In Enshrouded, tearing down a wall to "optimize" the layout can wipe a teammate's carefully placed workshop. The rule is simple: shared structures need shared consent. Build your own annex, mark it as yours, and do whatever you like there. Touch the commons only after a quick "hey, mind if I rework the storage?"
Rule Two: Contribute Before You Consume
Every survival group quietly tracks one thing, even if nobody says it out loud: who gives to the pool and who only takes from it. The player who tosses their spare ore into the shared chest is building trust. The player who empties the shared chest of everyone's healing items right before a boss fight is spending it.
The etiquette here is not communism, it is proportion. If you pull ten stacks of stone out of shared storage for your personal mega-project, put something back. If you use the group's food, help farm it. Resentment on a co-op server almost never comes from a single big betrayal. It builds slowly, one unreciprocated withdrawal at a time, until someone finally says "why am I the only one farming?" Head that off by being visibly generous with the pool. Our Valheim multiplayer guide and Enshrouded multiplayer guide both lean on the same truth: shared progress only works when contribution is shared too.
Rule Three: Know Whose World It Is
There is a real distinction between a hosted world and a dedicated server, and it changes the etiquette.
When you are playing in a friend's hosted world, you are a guest in their house. The game only exists when they log on, their progress is the canonical save, and they carry the responsibility of keeping it alive. Guests should defer accordingly: you do not demand marathon sessions from a host, you do not sulk when they want to log off, and you understand that if they stop playing, the world stops.
A dedicated server flattens that hierarchy. Now the world exists independently, anyone can play when they want, and the ownership becomes genuinely collective. That is exactly why serious groups graduate to dedicated hosting: it removes the "we can only play when the host is on" bottleneck and turns a fragile arrangement into a durable one. If your group keeps stalling because the world lives on one person's machine, that is usually the signal to move to a dedicated server, as our Palworld server hosting guide and Rust server setup guide both walk through.
Rule Four: Griefing Is Defined by Consent, Not by the Game
Here is the nuance that trips people up. Whether an action is griefing depends almost entirely on what everyone agreed the server is.
On a declared PvP server, raiding a rival base is the game. Nobody is a victim, because everyone signed up for a world where that is allowed. On a PvE co-op server, the exact same action, breaking into a teammate's stash or killing them for their loot, is a betrayal that ends friendships. The action is identical. The consent is not.
So the real rule is: establish what kind of server this is before anyone builds anything they care about. Is this friendly PvE where the enemy is the world? Is it PvP where trust is a luxury and walls are a necessity? Is it somewhere in between with agreed truces? A five-minute conversation on day one prevents the single most common survival-server blowup, which is one player doing something they thought was fair game while everyone else experiences it as a stab in the back.
Rule Five: Respect the Pace Mismatch
Not everyone plays at the same speed, and a co-op server is where that becomes a social problem. One player grinds twelve hours and unlocks the next tier. Another logs on twice a week. Suddenly the fast player is bored waiting, and the slow player feels left behind and locked out of content they never got to experience.
Good groups manage this deliberately. The common courtesies: do not rush ahead through shared story or boss content without the group, because being present for the big moments is half the point of playing together. If you must progress solo, focus on infrastructure that helps everyone, farming, building, and prepping, rather than consuming the milestones the group wanted to hit as a team. In Once Human or Valheim, blowing through a boss the group was saving for a weekend session is a small thing that leaves a big mark. Our Once Human beginners guide is a good primer for keeping a group roughly in sync on progression.
Rule Six: Log Off Like a Considerate Adult
The quietest etiquette rule is about how you leave, both for the night and for good.
For the night: do not log off mid-crisis and leave a teammate holding the bag. Bailing the second a raid starts or a base is on fire, then reappearing tomorrow like nothing happened, is a fast way to lose standing. If you have to go, say so, and help stabilize things first if you can.
For good: people drift away from survival servers, and that is normal. The graceful version is to say it out loud. "I think I am done with this world" gives the group closure and a chance to redistribute your role. The ungraceful version is to simply stop showing up, leaving your unfinished projects and your share of the work as a silent gap everyone has to route around. A survival server is a small society. Leaving well is part of belonging to it.
The Bottom Line
Co-op survival is one of gaming's best social experiences precisely because it demands trust. The unwritten rules all point at the same thing: you are sharing a world, so act like the other people in it are real. Respect the commons, give before you take, know whose world it is, agree on what the server actually is, move at a pace that includes everyone, and leave with a word rather than a gap. None of it is in the tutorial. All of it is the difference between a server that becomes a story you tell for years and one that quietly dies in a week. If you are about to start a new world with friends, spend five minutes agreeing on these before you place your first workbench. It is the most important crafting recipe in the game.
