> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/forge/forge-basics-and-ui/forge-interface/folders/basic-folder-structure.md).

# Basic Folder Structure

Examples of a basic folder structure to use on Halo Infinite Forge maps.

<figure><img src="https://692276616-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN06Vv6nlwviUQ4hI2Kkd%2Fuploads%2Fgit-blob-74e137057d6f7b94c14119a6cbc4254a8f2c8ecf%2Fcover-tsg-placeholder.jpg?alt=media" alt="Cover image"><figcaption></figcaption></figure>

The folder structure doesn't have to be overly complicated to work efficiently. Below are some examples of basic folder structures that experienced forgers have come up with, and are tuned to work for the common object groups in a Forge map. A basic folder structure is useful for categorizing objects into large categories that still differentiate them enough to be understandable.

## Advantages

The advantages to having a basic folder structure are:

* Fast to set up
* Easy to understand
* Easier to get forgers to use it who are unfamiliar or against using the Folders tab
* Less budget usage, as every folder takes up Forge Simulation Memory. This is only really an issue on maps that are nearing 100% Forge Simulation Memory and really need to scrape the bottom of the optimization barrel to botch together the map being just under the forging budget limits.

## Disadvantages

The disadvantages to having a basic folder structure are:

* Some objects will not be organized to descriptive enough folders
* Selecting specific groups of objects is more difficult as objects from multiple categories may be in the same folder
* It may take longer to find specific objects due to multiple objects of different types being in the same folder

## Examples

Examples of basic folder structures used by experienced forgers:

### MikRips

<details>

<summary>General</summary>

* 00 Blockout
* 01 Sandbox
  * Gamemodes
  * Lighting
  * Misc.
  * Nav Mesh
  * Spawns
  * Vehicles
  * Volumes
  * Weapons Equipment
* 02 Scripts
* 03 Containment
* 04 Art

</details>

## timmyforges

<details>

<summary>General</summary>

* Art
* Blockers
* Blockout
* Dynamic
* Emissives
* Gameplay

</details>

If you're confused what the `root folder` means, see [Set as Root Folder](/forge/forge-basics-and-ui/forge-interface/folders.md#set-as-root-folder)

***

#### <mark style="color:green;">Contributors</mark>

Okom\
MikRips\
timmyforges


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.thescriptersguild.com/forge/forge-basics-and-ui/forge-interface/folders/basic-folder-structure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.