> For the complete documentation index, see [llms.txt](https://docs.sandbox.game/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sandbox.game/en/creator/game-maker/game-production-guide/blockout.md).
# Blockout
TIPS FOR BEGINNERS
Try to add a little variation in the height of your world and don't be afraid to delete blocks to make the base, or surface, of your world smaller to finish by the deadline.
> **Game Production Guide Navigation**\
> :red\_square:[Concept](/en/creator/game-maker/game-production-guide/concept.md) :orange\_square:[Blockout](/en/creator/game-maker/game-production-guide/blockout.md) :yellow\_square:[Logic](/en/creator/game-maker/game-production-guide/logic.md) :green\_square:[Art](/en/creator/game-maker/game-production-guide/art.md) \
> :blue\_square:[Quality Assurance](/en/creator/game-maker/game-production-guide/quality-assurance.md) :purple\_square:[Polish](/en/creator/game-maker/game-production-guide/polish.md) :white\_large\_square:[Marketing](/en/creator/game-maker/game-production-guide/marketing.md)
## **2. CREATIVE CONCEPT**
{% tabs %}
{% tab title="Mission 1" %}
### **DEFINE ENTRIES & EXITS**
For every playspace planned, how will players enter and exit those spaces for the visual impact needed (hallways, doors, teleporting, etc)? Create a sketch for each playspace with entries and exits marked.
How will those spaces be connected to each other? What will the player see while moving through these transitions? How can you improve transitions for the best aesthethics and feel?
{% endtab %}
{% tab title="Mission 2" %}
### SKETCH & BUILD A MINI BASEMAP
{% hint style="success" %}
**LEVERAGE VERTICAL SPACE**
Think outside the box to use as much space as possible to add more gameplay.
{% endhint %}
Arrange sketches from Mission 1 with gameplay areas in sequence (if gameplay is linear). Visualise how play in each area will be connected to others.
Create a [**Rough Basemap**](/en/creator/game-maker/creative-guides/experience-design-techniques/3d-spatial-layout/rough-base-map.md). VoxEdit is an excellent tool to build a scale map of your Experience (1 voxel : 1 block) to guide the next step of greyboxing because you can select and move voxels. In Game Maker, you can not move blocks, and it's much easier to work on a smaller scale.
{% endtab %}
{% tab title="Mission 3" %}
### BEGIN GREYBOXING
Use your rough basemap as a guide to create the basic 3D shape of your Experience with blocks only. For now, stick with very basic colours or simply grey. See [**Greyboxing**](/en/creator/game-maker/creative-guides/experience-design-techniques/3d-spatial-layout/greyboxing-blockout.md)**.**
{% endtab %}
{% endtabs %}
## **3. ALPHA PRODUCTION**
{% tabs %}
{% tab title="Mission 4" %}
### ADD LARGE ASSETS
Place the largest assets that will frame out gameplay spaces visually or provide access to other areas. Modify blocks if needed to fit these pieces.
### TEST
Press TAB to explore the whole Experience to ensure:
* Gameplay areas provide enough space for player interactions with objects
* Entries and exits of gameplay areas align naturally
* Entries and exits align to your visual hierarchy
Modify as needed.
{% endtab %}
{% tab title="Mission 5" %}
### ADD VISUAL EMPHASIS/TEXTURE
Begin adding colour and texture blocks with variation without pattern, avoiding overuse of texture and conflicting textures. Create paths to guide players through gameplay areas and stay focused. See [**Blockout Aesthetics**](/en/creator/game-maker/creative-guides/experience-design-techniques/art-design/blockout-aesthetics.md).
### TEST
Press TAB to enter play mode and test how the world will feel for the player. Do the colours and patterns used in your blockout help them stay on the right track? Do they help players find surprises? Is it comfortable for the eyes?
{% endtab %}
{% endtabs %}
---
# 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.sandbox.game/en/creator/game-maker/game-production-guide/blockout.md?ask=&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.