> For the complete documentation index, see [llms.txt](https://docs.dunedocker.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dunedocker.app/community-services/base-builder.md).

# Dune Docker Base Builder

[Dune Docker Base Builder](https://blueprints.dunedocker.app/) is a browser-based 3D planning and sharing tool for **Dune: Awakening** bases. Use it to experiment with a layout before committing time and materials in game.

## What You Can Do

* Browse a searchable catalog of structures and placeables.
* Place, snap, move, rotate, duplicate, and inspect pieces in 3D.
* Check collisions and plan coverage across multiple land claims.
* Preview a design from different angles, switch between day and night, and walk through the layout.
* Capture screenshots and import or export supported base layouts.
* Save public, unlisted, or private projects after signing in as a community member.
* Explore shared community designs and make an editable copy as a starting point.

The Base Builder is also linked from the Dune Docker Console footer. It runs in your browser and does not require access to your server's Console.

{% hint style="warning" %}
The Base Builder is a planning aid. Game updates, missing assets, terrain, stability rules, and world restrictions can affect whether a design can be built exactly as shown. Keep a backup before importing or replacing game data.
{% endhint %}

[Open Dune Docker Base Builder](https://blueprints.dunedocker.app/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dunedocker.app/community-services/base-builder.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
