Navigation
Community
Configuring
Creating
FAQ - General
Info for Sauerbraten Users
Introduction
Known Issues
Main Page
Notes
Playing
Troubleshooting

Creating >

### Introduction

The basic process for working on a map is as follows:
Remember, the client and server have their own copy of the map, including the script! This is generally automatically synchronized, but if you edit your local copy, it will be out of sync until you upload it.

### Uploading

'Upload map' in the main menu will do the following:

- Check for syntax errors in map.js
- Save the entities to entities.json
- Save the map to map.ogz
- Package the entities, map.ogz and map.js, as well as other relevant files in the map directory, into a single archive (MAPNAME.tar.gz)
- Upload the archive to Syntensity
- Notify the server instance that the map was updated, which will lead the server instance to get the new map and run it, and after that tell all connected clients to get and run the new map as well (for you, the uploading client, the map is already present in the latest version, so nothing will be downloaded)

### Backups

It is very important to back up your work frequently, this is true of any software, but especially of alpha software like Syntensity. The following steps can be done to save your work:

- Save entities in the menu, to save the current entities to a file. If you use the same filename as the current one (typically entities.json), it will be overwritten.
- /savemap will save the map geometry (not entities), overwriting the current file. That means that your local copy will differ from the server, until you upload it. /savemap [NAME] lets you save under a different name, which is useful for backup purposes [[?]]
- You can create clones of your assets, on the master server. This saves a separate copy of the asset on the master, which you can use later, if for example you change the original and you want to go back to the old version.

Updated on Aug 9, 2009 by Alon Zakai (Version 5)