> For the complete documentation index, see [llms.txt](https://pokecloud.gitbook.io/pokecloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pokecloud.gitbook.io/pokecloud/master/admin-guides/nest-management/creating-nests.md).

# Creating Nests

How to create nests using the default and extend versions of the $create-nest command for faster data input.

{% hint style="danger" %}
**Before continuing, ensure your server has completed the community setup guide.**
{% endhint %}

{% content-ref url="/pages/-LmjYfq9yiLbVckBliRy" %}
[Community Setup](/pokecloud/master/admin-guides/community-setup.md)
{% endcontent-ref %}

### Generated Nest Location

The [**city**](https://pokecloud.gitbook.io/pokecloud/guides/community-setup/location-settings#city) and [**state**](https://pokecloud.gitbook.io/pokecloud/guides/community-setup/location-settings#state) from your sever settings is automatically attached to the new nest being created. If the server covers more than one city, you can change the default active city any time using [**this command**](https://pokecloud.gitbook.io/pokecloud/guides/community-setup/location-settings#city). 

> *Its recommended to create all nests for one city, then change the city and continue creating all nests for that city.*

### Generated Directions

Upon creating a nest, directions are automatically generated using the nest name as well as the servers [**city**](https://pokecloud.gitbook.io/pokecloud/guides/community-setup/location-settings#city) and [**state**](https://pokecloud.gitbook.io/pokecloud/guides/community-setup/location-settings#state). This feature uses Google to automatically find the users location to provide faster and more accurate directions.

{% hint style="warning" %}
**PokeCloud does NOT read, store or share user locations in anyway.**
{% endhint %}

### Full Command

Only the nest name is required. Optionally, the amount of pokestops, gyms and spawns can be inputted by separating each with a comma. Don't worry, nest data can be updated at any time. Lets take a look at what the full command looks like as well as an example...

{% tabs %}
{% tab title="Full Command" %}

```
$create-nest [pokestops], [gyms], [spawns], [exgyms]
```

*< > = required    \[ ] = optional*
{% endtab %}

{% tab title="Alias" %}

```
$cn [pokestops], [gyms], [spawns], [exgyms]
```

*< > = required    \[ ] = optional*
{% endtab %}

{% tab title="Example" %}

```
$cn hilton park, 5, 3, 8, 1
```

This creates a nest called **Hilton Park** with **5** pokestops, **3** gyms, **8** spawns and **1** ex raid gym.
{% endtab %}
{% endtabs %}

### Using Name Only

Creating a nest with just the name defaults all nest data to the unknown state of **?**.

```
$cn hilton park
```

> *Creates a nest called **Hilton Park** with **?** pokestops, **?** gyms and **?** spawns.*

### Skipping Inputs

Skipping inputs are also possible by using a **?** for the amount. This is only needed if the input after another input is being set *(as shown below)*.

```
$cn hilton park, ?, 3
```

> *Creates a nest called **Hilton Park** with **?** pokestops, **3 gyms*** ***?** spawns, and **?** ex gyms. Notice we left the spawn and ex gym input blank to default it to its default value of **?**/**0**.*