Running a healthy Eco server, pacing, meteor timing, and player onboarding

Eco is unusual among multiplayer games: it has a real beginning, middle, and end. The world spawns. Civilization develops. The meteor approaches. Either humanity coordinates and survives, or it doesn't.

The fun is in the arc. A badly-paced Eco server burns out players before the arc completes, and the world dies not from the meteor but from disengagement.

This article is what we've learned about pacing an Eco server so it actually finishes.

The default schedule

By default, the meteor lands 30 real-life days after server start. Server admins adjust this via MeteorImpactDays in Difficulty.eco. Common modifications:

• Real-world week to meteor: aggressive, only for very active groups.
• Real-world month to meteor: the most common choice.
• Real-world 3 months to meteor: marathon mode, requires committed players.

The right pacing depends on your group's expected play hours. A group playing 4 hours a week needs a longer timeline than one playing 4 hours a day.

The 60-day arc

The arc as a mermaid timeline

Player onboarding is your bottleneck

The first 2 hours of an Eco player's experience are the hardest. They have:

• No tech (everything must be hand-crafted).
• No money.
• A confusing skill tree.
• Hunger and fatigue mechanics.
• No clear path forward.

If you don't help them through this, they bounce. The number-one reason Eco servers die: not enough players make it past hour 2.

What helps:

Spawn area orientation. Build a small spawn village with signs explaining: where to find food, how to chop trees, how to set up a basic shelter, what skills to consider taking first.

A starter pack (small, free, in a publicly accessible chest at spawn): a few basic tools, some seeds, a few logs. Lower the threshold without removing the survival feel.

Discord help. New players ask questions. Have someone available. The first 3 days of a new player's experience determines if they stick.

The middle game: too much freedom, not enough goals

After the first hour, players are okay technically but often lost socially. The mid-game is when most servers stall.

What helps:

Clear early laws. Pass a few basic laws within the first 3 days. Even silly ones. The point is to demonstrate that the government works and that players can shape policy.

Public infrastructure projects. Sponsor (with admin powers if needed) a road network, a town hall, a market. Concrete goals players can contribute to.

Economic seed. Help establish currency early. Even a tiny "treasury" of money distributed equally can kickstart trade.

The election problem

Eco elections happen on game-time schedules. They are a wonderful mechanic that can also be a community-killer if mismanaged.

Common failure modes:

• Single candidate runs unopposed. Boring election, weak mandate.
• Two candidates run and one ghost-leaves the server after losing. Salt.
• Election cycles too fast. Players hardly settle before re-electing.
• No one runs at all. Government stalls.

Mitigations:

• Encourage candidates early. A week before each election, post in Discord: "Election coming. Who wants to run?" Some peer pressure helps.
• Lengthen election cycles for small servers. The default may be too fast.
• Make candidacy easy. No high barriers, no required cost.

Pacing technology

Eco's tech tree is sized for default settings. If you increase player time available (a 90-day server with active players), tech advances fast and the back half of the game is empty.

Mitigations:

• Crank up skill cost to slow tech progression.
• Limit specializations early. Encourage players to pick 2 skill paths, not 5.
• Adjust resource scarcity. More scarce = more interdependence, slower tech.

The right values depend on your timeline. Test on a private side server before settling.

Pollution and waste, the dramatic middle act

Eco's pollution mechanics are the most "Eco" part of Eco. By mid-game, the world's environment starts visibly degrading from industry. Smog, dead plants, contaminated water.

This is the moment your server's drama peaks. Players will:

• Debate whether to regulate industry.
• Propose laws.
• Fight about them.
• Either solve the problem or watch the world die before the meteor.

Your job as admin: don't intervene. The drama is the game. Let the players figure it out. If you intervene with emergency env tweaks because pollution is "unrealistically high," you've taken away the moment of the playthrough that makes Eco different from Minecraft.

The meteor approach

Final weeks before meteor impact. The community either has unified around a meteor-deflection project or is fragmented.

What helps:

• Public progress visibility. Make sure all players can see, on a sign or screen, "Meteor deflection: 47% complete."
• Late-game economic injection. If the project is stalling for lack of resources, the admin can (with announcement) inject some currency or materials to keep momentum.
• Endgame events. Pre-meteor speeches, voluntary roleplay. Some groups love this.

After the meteor

If the meteor is deflected: celebration. Optionally, allow the world to continue in "post-arc" mode. Players can keep building.

If the meteor hits: the world becomes desolate. Some groups treat this as a learning experience and immediately want to restart with better policy. Others mourn.

Either way, plan what comes next. A successful Eco playthrough should be followed by:

• A retrospective discussion (what worked, what didn't).
• A short break.
• Either a fresh world or a different game.

Don't immediately restart. Players need to digest.

Sizing the experience

For a small group (4 to 6 active players):

• 60-day to 90-day timeline.
• Aggressive onboarding support.
• Higher tech-progression speed (smaller groups can't sustain a slow grind).

For a community (10 to 25 players):

• Default to 30 to 60 days timeline depending on activity.
• Less hand-holding (community will self-organize).
• Default tech speed.

For a classroom or structured cohort:

• 30-day timeline aligned to the course schedule.
• Heavy onboarding (assume some players will play one hour total).
• Clear rules and educational framing.

Common admin mistakes

Skipping onboarding. "They'll figure it out" leaves half your prospective players bouncing in week 1.

Over-policing the economy. Letting the game's emergent economy develop, even chaotically, is the point. Don't fix it unless it's truly broken.

Restarting too soon. A 4-day-old Eco server that one player griefed is not a failed playthrough. Talk to the players. See what they want.

Resetting mid-arc. Devastating to player trust. Only do this if the world is unfixably broken.

Treating it like Minecraft. Eco rewards different admin behaviors. Lower friction at start, higher trust in the middle, support at the end.

A starting calendar

For a 60-day Eco server with a small group:

Phase	When	Admin focus
Onboarding	Day 1-3	Spawn area, starter pack, all-hands help
First politics	Day 4-7	First election, first law, sponsored project
Industrial revolution	Day 7-21	Step back. Let players build.
Environmental crisis	Day 21-40	Don't intervene. Drama is the game.
Mobilization	Day 40-50	Make project progress visible. Maybe seed resources.
Endgame	Day 50-60	Events, speeches, finale.
Retrospective	Day 60+	Pause. Discuss. Decide what's next.

Adjust to your group's pace, but expect a similar arc.

Conclusion

Eco is a story-shaped game. Your job as admin is to facilitate the story, not control it. Onboard hard, let the middle game breathe, don't intervene in the drama, and plan the ending. Get this right and Eco is one of the most rewarding multiplayer experiences you can offer. Get it wrong and you have a half-empty server arguing about taxation.