> ## Documentation Index
> Fetch the complete documentation index at: https://docs.summerengine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Make a game like Minecraft

> Build a shared survival or sandbox world like a Minecraft server with Summer Engine: a persistent World that saves, sleeps and wakes, plus player saves and chat.

A survival or sandbox game is a place, not a match. Players build something
together, log off, and come back days later to find it exactly as they left
it. Summer keeps that World on a server, saves it, lets it sleep while nobody
is online, and wakes it when the next player joins. This page shows how the
pieces fit together.

## The pieces you need

> [card] [Make a multiplayer game on Summer Games](https://docs.summerengine.com/build/multiplayer.md)
>
> Your server runs the World; every player runs the same game.

> [card] [Persistent worlds](https://docs.summerengine.com/build/persistent-worlds.md)
>
> A World that saves, sleeps when empty and wakes when someone joins.

> [card] [Save player progress](https://docs.summerengine.com/build/player-progress.md)
>
> Each player's inventory and skills follow them between sessions.

> [card] [Shared game world](https://docs.summerengine.com/build/shared-state.md)
>
> Every placed block, chest and door, the same for everyone.

> [card] [Instant movement](https://docs.summerengine.com/build/movement.md)
>
> Running, jumping and building respond the moment you press a key.

> [card] [Friends and messages](https://docs.summerengine.com/build/friends.md)
>
> See which friends are online and in your game.

> [card] [Text chat](https://docs.summerengine.com/build/chat.md)
>
> Talk to everyone in the World.

> [card] [Server size](https://docs.summerengine.com/build/server-size.md)
>
> Pick how much server a World gets and how many players it holds.

> [card] [Console commands](https://docs.summerengine.com/build/console-commands.md)
>
> Run admin commands in a live World.

> [card] [Cosmetics](https://docs.summerengine.com/build/cosmetics.md)
>
> Skins and outfits players own and wear in every World.

## How it fits together

![The survival loop: a player joins their World, builds with others, the server saves the World, the World sleeps when nobody is online, and it wakes right where it was when the next player joins.](https://mintcdn.com/summer-18f03259/_ENGS2HrEIacSS6a/images/guide-art/games-like/survival-sandbox-light.svg?fit=max\&auto=format\&n=_ENGS2HrEIacSS6a\&q=85\&s=6a875699c309c7ed1341eb3860b97664)

A player opens one of their Worlds and joins it. While people play, your
server saves the World at regular checkpoints and before it stops. When the
last player leaves, the World goes to sleep. The next player to join wakes it,
and the server restores the last save before anyone walks in.

## Plan my game

**Plan my survival game.** Your agent reads your project and lays out the Summer pieces in the order to build them.

I'm making a shared survival or sandbox game like a Minecraft server in
Summer. Read my project and plan how to build it with these Summer skills, in
this order; if you don't have them installed, find them in the Summer
library:

1. `multiplayer` and `multiplayer-project`: the server and client scenes and
   a first Local Play run.
2. `multiplayer-movement`: each player moves their own character instantly.
3. `multiplayer-state`: placed blocks, chests and doors, owned by the server.
4. `summer-world-saves`: the World saves, sleeps and restores.
5. `summer-player-data`: each player's inventory follows them.
6. `summer-world-chat` and `summer-friends`: talk in the World and see
   friends.

For each step, tell me what changes in my project and what I'll see when I
test it. Don't change any files yet.

## Build the signature features

### A World that remembers everything

**Make my World persistent.** Builds survive restarts, and the World restores before anyone joins.

In my Summer project, make my World persistent: everything players build is
saved on the server and is still there after the World sleeps and wakes. Use
the Summer `summer-world-saves` skill; if you don't have it installed, find it
in the Summer library.

* Save at regular checkpoints, and once more before the World stops.
* Restore the last save before the first player is let in.
* Keep the save format the same across game updates, so existing Worlds keep
  loading.

Read my project first and tell me what my World needs to save. Then test it
with Local Play and tell me what you saw, and what only a hosted World proves.

### Inventories that follow the player

**Save each player's inventory.** It follows them to every World.

In my Summer project, save each player's inventory and stats so they follow
the player between sessions. Use the Summer `summer-player-data` skill; if you
don't have it installed, find it in the Summer library.

Load the player's save when they join, save when it changes and when they
leave, and make sure a crash never loses more than a few seconds. Read my
project first, then test it with Local Play and tell me what you saw.

***

Does this not help you? [Reach out on Discord!](https://discord.gg/summerengine)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.