<cat>Play.Hosting</cat> <title>Getting started with your rust server</title> <note>This article is assuming that you already have the rust server files installed and that you know how to start your server, if you don't then please refer to <page>Creating-a-server</page>. This is miscellaneous information about the rust server that does not need its own page. Refer to the other pages on the left too.</note> # server.identity Files <upload src="9f298/8dc907b9c7ee83b.png" size="14974" name="serverident.png" /> When you start your server up with a server.identity these are the files stored in that folder. It allows you to run multiple servers from the same install. Rust uses a journaling technique with its database(db) files. This is the reason you will see a `-wal` file with those. You can [click here to read about WAL](https://sqlite.org/wal.html). The number at the end before the extension is referred to the protocol version, at forced updates this will always increase. So next time they decide to force a blueprint wipe, the 5 will change to 6. All of these files are safe to delete at forced wipe(except companion.id). It is dangerous and ill-advised to just rename an old sav in an attempt to circumvent the forced wipe. When you start your server up with a server.identity these are the files stored in that folder. It allows you to run multiple servers from the same install. ⤶ Rust uses a journaling technique with its database(db) files. This is the reason you will see a `-wal` file with those. You can [click here to read about WAL](https://sqlite.org/wal.html).⤶ ⤶ The number at the end before the extension is referred to as the protocol version. It increases at a forced wipe forcing your server to create a new one and not use the old. Generally it only happens with the sav file because they only force a map wipe. If you wanted to force a blueprint wipe you would need to delete the blueprints file at the same time. It is dangerous and ill-advised to just rename an old sav in an attempt to circumvent the forced wipe.⤶ | Folder/File | Notes | | --------------------- | -------------------------------------------------------------------------------------- | | cfg | Folder - cfg files for your admins and banned players, and where you store server.cfg for settings | | loadouts | Folder - json files from using the saveloadout command | | serveremoji | Folder - for your custom server emojis, see <page>Server Custom Emojis</page> | | companion.id | This is a unique identifier for your server used with rust+ see <page>Rust+ Server</page> | | serveremoji | Folder - for your custom server emojis, see <page>server-custom-emojis</page> | | companion.id | This is a unique identifier for your server used with rust+ see <page>rust-companion-server</page> | | Log.EAC | unknown | | player.blueprints | This file stores your players blueprints | | player.deaths | This file stores information about player deaths so they can know who and why when they login | | player.identities | unknown | | player.states | unknown | | player.tokens | Stores a unique token for players that pair with rust+ Removing this will force players to repair | | *.sav | This file holds all map data and entities, player buildings, deployables and more. It should have the same name as the map. The server creates and keeps backups every time the server saves(not pictured) | | *.map | The map file; terrain, monuments, etc. Normal proc gen maps are proceduralmap.SIZE.SEED.map but custom maps could be named anything. | | sv.files | This file stores player signs and pictures from the contact system | #Links & FAQ srtbull covers a lot about being an admin, and has been making admin videos for a long time. If you learn more from seeing check out the [Start A Rust Server Tutorial](https://www.youtube.com/watch?v=_Lk7CuTMqoY) and others on his channel. Steam support on [what is and how to find a steamID](https://help.steampowered.com/en/faqs/view/2816-BE67-5B69-0FEC)