Maps

Maps are used together with game data to create maps with things such as spawn-points to be used with your game.

Maps are meant to be used as a way to store information about a map in your game. A map can be used to store spawn points that you later can access from your game.

A map can contain the following information;

Property	Description	Required
game_id	Id of the game the map should belong to	Yes
name	Name of the map	Yes
asset_id	The ID of an asset if you've created one and don't want this call to do it for you.	No
spawn_points	An array of spawn point objects. See below.	No

Spawn Points

Spawn points have a few extra properties inside that can be added.

Property	Description	Required
position	Coordinates for where the spawn point should be positioned	Yes
rotation	Coordinates for the rotation of the spawn point	Yes
name	Name of the spawn point	Yes
guid	A 38-character long unique identifier provided by you	No
cameras	An array of cameras for the spawn point. See below.	No

Maps are meant to be used together with content from your game.

Creating a map is done by using our Admin API.

When creating a map, you send a POST request with the payload data. This will create the map, an asset for it and spawn points with their own assets for each spawn point you've sent along.

You can send the request with something like https://www.postman.com/ or by calling the Admin API from a tool that you've created or with a custom editor-script in your game engine.

Do not include any Admin API functionality or information in a public build

If you make a tool or create a way to use the Admin API inside of the game engine you are using, make sure that it is not included in a public build. Leaking the Admin API information can have devastating consequences for your game as it allow players to login and change anything in the LootLocker web console.

You can read more about maps in our Admin API documentation.