> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dietrich-development.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> AI relationship management and ambient spawn control system for RedM servers

A modular, fully configurable RedM script that gives server owners complete control over AI relationship behavior, ambient spawn density, location-based ped restrictions, and visual model overrides. Whether you want faction conflicts, living town behaviors, or optimized performance zones - this script covers all of it.

<Info>
  This script provides control over AI relationships, spawn frequencies, location restrictions, and visual model replacements to create immersive and optimized server environments.
</Info>

## Features

<Columns cols={2}>
  <Card title="Relationship control" icon="users">
    Define default AI-to-AI relationships globally, configure group behaviors toward players, and set conditional rules based on time, job, weather, and more.
  </Card>

  <Card title="Spawn frequency management" icon="chart-line">
    Globally control ped, animal, and traffic spawn density with area-specific overrides for different zones and events.
  </Card>

  <Card title="Volume-based restrictions" icon="location-dot">
    Define boxes or spheres to control AI spawn types in key locations, blocking specific ped types like dangerous animals, town NPCs, lawmen, and birds.
  </Card>

  <Card title="Model replacements" icon="user-pen">
    Replace the visual appearance of specific peds in defined areas while maintaining original model logic for animations and behavior.
  </Card>

  <Card title="Debugging tools" icon="bug">
    Toggle debug mode for verbose logs and define custom conditions as Lua functions directly in the configuration.
  </Card>

  <Card title="Framework integration" icon="gears">
    Compatible with VORP Core and RSG Core frameworks with modular framework bridge support.
  </Card>
</Columns>

## Limitations

* **Volume names**: Volume names must exist in the game map or be manually created
* **Model replacements**: Only affect visual appearance, not base behavior
* **Relationship persistence**: Only `rel_cop` and `player` relationships are enforced continuously
* **Condition functions**: Must return boolean values and be properly formatted

## Next steps

<Columns cols={2}>
  <Card title="Setup" icon="screwdriver-wrench" href="/scripts/ambient-ped-manager/setup">
    Installation, relationship rules, spawn frequencies, and restrictions.
  </Card>

  <Card title="Docs home" icon="book-open" href="/">
    Installation basics and links to every script.
  </Card>
</Columns>