Requirements and Installation

Read this before anything else. Most first-run problems are a missing package rather than a mistake in your scene.

Unity version

CIVIL-AI-SYSTEM 0.13.0 is developed and tested against Unity 6000.3 (Unity 6.3).

Newer Unity 6 patch releases are expected to work. If you are on an older LTS such as 2022.3, expect compile errors around the UI Toolkit editors and the AI Navigation API, which both changed in Unity 6.

Render pipeline

The tool ships configured for the Universal Render Pipeline (URP), which is what the example scenes and materials are authored against.

Built-In and HDRP are supported through material packages you import yourself:

Pipeline	What to do
URP	Nothing. This is the default.
Built-In	Import Assets/BardTreeLtd/RenderPipelines/BardTreeLtd-BuiltIn.unitypackage
HDRP	Import Assets/BardTreeLtd/RenderPipelines/BardTreeLtd-HDRP.unitypackage

Double-click the .unitypackage in the Project window and accept the import. It replaces the shipped materials with versions built for your pipeline.

If you skip this step on a Built-In or HDRP project, everything still runs — the example scenes just render magenta, because the materials reference shaders your pipeline does not have.

Required packages

Install these from Window > Package Manager before importing, or let Unity pull them in as dependencies.

Package	Identifier	Why it is needed
AI Navigation	com.unity.ai.navigation	NavMeshSurface, used by the default UNITY nav mode
Input System	com.unity.inputsystem	The example player controller and dialogue input
TextMeshPro	bundled with com.unity.ugui	On-screen clock, overhead text, editor labels
Cinemachine	com.unity.cinemachine	Only needed for DIALOGUE-SYSTEM camera work

Two notes worth knowing:

• TextMeshPro needs its Essentials imported, not just the package installed. Unity prompts for this the first time you open a scene using TMP (Window > TextMeshPro > Import TMP Essential Resources). Without it, overhead dialogue text degrades gracefully to a no-op rather than erroring, so the symptom is silently missing text rather than a red console.
• Cinemachine is only a DIALOGUE-SYSTEM dependency. A CivilAI-only project does not need it.

Importing the asset

1. Open Window > Package Manager, switch the dropdown to My Assets, find CIVIL AI SYSTEM, and click Import.
2. Accept the full import the first time. Everything lands under Assets/BardTreeLtd/.
3. The Welcome window opens automatically after import. It lists your installed Bard Tree products and walks you through the first four steps.

You can reopen the Welcome window at any time from BardTreeLtd/Welcome. If you want it to behave as though this were a fresh install again, use BardTreeLtd/Help/Reset Welcome State.

What gets installed

The asset installs as a set of modules under one root, which is why the editor menu is grouped under BardTreeLtd rather than per-product:

Folder	Contents
Assets/BardTreeLtd/CIVIL-AI-SYSTEM	The main product
Assets/BardTreeLtd/Shared	Services shared across Bard Tree products
Assets/BardTreeLtd/SAVE-SYSTEM	Save and load support
Assets/BardTreeLtd/SENSE-SYSTEM	Agent perception
Assets/BardTreeLtd/Resources	The canonical resource root for generated and module-owned assets
Assets/BardTreeLtd/RenderPipelines	The Built-In and HDRP material packages

Assets/BardTreeLtd/Resources is the one to remember — it is where behaviour tree repositories, module settings and other generated assets live.

Upgrading from 0.12.x

0.13.0 restructured the asset into modules and moved the editor menu under a shared BardTreeLtd root. Two migration steps:

1. Repair your scenes. Run BardTreeLtd/Civil AI/Tool/Repair Scene For V0.13.0 with each of your scenes open. This updates scene objects to the current runtime entry point.
2. Remove the old readme files. Run BardTreeLtd/Help/Remove Legacy Readme Files. Importing a .unitypackage never deletes anything, so the old Readme.asset and TutorialInfo folder survive an in-place upgrade even though 0.13.0 no longer uses them.

The scene entry point also changed: ModuleService was replaced by BardTreeModuleBootstrap. The repair tool handles this for existing scenes.

See Upgrade Process for the full procedure and the changelog for everything that changed.

Next step

Continue to Your First Scene and get agents moving before you configure anything.