> For the complete documentation index, see [llms.txt](https://mindcodeinteractive.gitbook.io/easy-build-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mindcodeinteractive.gitbook.io/easy-build-system/meta/f.a.q.md).

# F.A.Q

### General

#### How many building parts can the system handle?

There's no hard limit. With batching/grouping enabled, games with 1,000+ placed parts run smoothly. For 5,000+ parts, make sure batching is active and consider using LODs on your models.

***

#### Does it work with the New Input System?

Both the New Input System and Legacy Input Manager are supported out of the box.\
The code uses `#if ENABLE_INPUT_SYSTEM` directives, so both paths coexist.\
Assign `InputActionReference` assets in the inspector when using the new system.

***

#### Can I build at runtime without a player controller?

You can call `BuildingManager.Instance.PlacePart()` from any script without a [Building Controller](/easy-build-system/reference/building-controller.md). The controller is only needed for interactive building with preview, raycasting, and input handling.

***

#### Can I use Easy Build System in a 2D game?

The system is designed for 3D, using Physics raycasting and 3D transforms.\
Adapting it to 2D requires a custom [Building View](/easy-build-system/reference/building-controller/building-view.md) with Physics2D raycasting and 2D collider support. This is possible but requires significant customization.

***

#### Does the system work in WebGL?

Yes, though file-based save providers may need adjustment due to restricted file access.\
Use PlayerPrefs as the save provider, or implement a custom server-side save adapter.


---

# 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://mindcodeinteractive.gitbook.io/easy-build-system/meta/f.a.q.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.